How to Upgrade Kudu During BDA V4.10/CDH 5.12 To BDA V4.11/CDH 5.13.1 Mammoth Upgrade
(Doc ID 2375323.1)
Last updated on APRIL 11, 2018
Big Data Appliance Integrated Software - Version 4.10.0 and later Linux x86-64
The steps here provide the prerequisite and post-upgrade steps for upgrading Kudu during a BDA V4.10/CDH 5.12.1 to V4.11/CDH5.13.1 Mammoth upgrade. The BDA V4.11 upgrade document, Upgrading Oracle Big Data Appliance(BDA) CDH Cluster to V4.11.0 from V4.7, V4.8, V4.9, V4.10 Releases using Mammoth Software Upgrade Bundle for OL6 (Doc ID 2346478.1) points to this note in the "Prerequisites for Kudu" section for detailed steps on how to complete the Kudu upgrade on a BDA V4.10 cluster which is being upgraded to BDA V4.11. The way to upgrade Kudu is to 1) remove the Kudu service from Cloudera Manager in the BDA V4.10 cluster 2) upgrade to BDA V4.11 and then 3) post-4.11 upgrade re-add the Kudu service with the same configuration as in 4.10.
Note: Cloudera confirms that there is no data loss when removing the Kudu service before upgrade and re-installing it after as long as Kudu is set up after upgrade with exactly the same configuration as before upgrade. Therefore to ensure no data loss it is mandatory that all Kudu configurations are set up exactly the same after upgrade as they were initially.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!