Upgrade Notes for Kudu 1.5.0 / CDH 5.13.0
Kudu 1.5 enables the optional ability to compute, store, and verify checksums on all pieces of data stored on a server by default. Due to storage format changes, downgrading to versions 1.3 or earlier is not supported and will result in an error.
Spark 2.2 (and higher) requires Java 8 at runtime even though Kudu Spark 2.x integration is Java 7 compatible. Spark 2.2 is the default dependency version as of Kudu 1.5.0.
The kudu-spark-tools module has been renamed to kudu-spark2-tools_2.11 in order to include the Spark and Scala base versions. This matches the pattern used in the kudu-spark module and artifacts.
To improve security, world-readable Kerberos keytab files are no longer accepted by default. Set --allow_world_readable_credentials=true to override this behavior. See KUDU-1955 for additional details.
Upgrade Kudu using Cloudera Manager
To use Cloudera Manager to upgrade Kudu using parcels or packages, use the following instructions. If you do not use Cloudera Manager, see Upgrade Kudu Using the Command Line.
Upgrade Kudu Using Parcels
Starting with Apache Kudu 1.5.0 / CDH 5.13, Kudu is part of the CDH parcel rather than a separate parcel. If you are upgrading from Kudu 1.4.x (or lower), you will need to first deactivate the existing Kudu parcel, and then activate the latest CDH parcel (CDH 5.13 and higher) that contains Kudu.
For instructions on upgrading CDH and its components using packages, see Upgrading to CDH 5.x Using Parcels.
Upgrade Kudu Using Packages
Starting with Apache Kudu 1.5.0 / CDH 5.13, Kudu ships with the CDH package. If you are upgrading from Kudu 1.4.x (or lower), you will need to first uninstall the existing Kudu packages, and then install the latest CDH package (CDH 5.13 and higher) that contains Kudu.
For instructions on upgrading CDH and its components using packages, see Upgrading to CDH 5.x Using Packages.
Upgrade Kudu Using the Command Line
If you use Cloudera Manager, do not use the following command-line instructions. See Upgrade Kudu using Cloudera Manager.
- If you use a repository, re-download the repository list file to ensure that you have the latest information.
- Stop the Kudu master and tablet servers using the following commands:
sudo service kudu-master stop sudo service kudu-tserver stop
- Depending on your operating system, issue the following set of commands on each Kudu host:
Operating System Upgrade Commands RHEL/CentOS
sudo yum -y clean all sudo yum -y upgrade kudu
sudo apt-get update sudo apt-get install kudu
sudo zypper clean --all sudo zypper update kudu
- Start the Kudu master and tablet servers using the following commands:
$ sudo service kudu-master start $ sudo service kudu-tserver start