Overview of Apache Kudu Installation and Upgrade in CDH
Starting with Apache Kudu 1.5.0 / CDH 5.13, Kudu ships with CDH 5. In a parcel-based configuration, Kudu is part of the CDH parcel rather than a separate parcel. The Kudu packages are also bundled into the CDH package.
On a cluster managed by Cloudera Manager, Kudu is installed as part of CDH and does not need to be installed separately. With Cloudera Manager, you can enable or disable the Kudu service, but the Kudu component remains present on the cluster. For instructions, see Installing Cloudera Manager and CDH.
On an unmanaged cluster, you can install Kudu packages manually. For instructions, see Kudu Installation.
Before you proceed with an upgrade, review the Upgrade Notes for Kudu 1.5.0 / CDH 5.13.0.
- If you have just upgraded Cloudera Manager from a version that did not include Kudu, then Kudu will not be installed automatically. You will need to add the Kudu service manually. Upgrading Cloudera Manager does not automatically upgrade CDH or other managed services.
- Parcels: If you are upgrading CDH and were previously using the standalone Kudu parcel (version 1.4.0 and lower), then you must deactivate this parcel and activate the latest CDH parcel that includes Kudu. For instructions, see Upgrading to CDH 5.x Using Parcels.
- Packages: If you are upgrading CDH and were previously using the Kudu package (version 1.4.0 and lower), then you must uninstall the kudu package and upgrade to the latest CDH package that includes Kudu. For instructions, see Upgrading to CDH 5.x Using Packages.
On an unmanaged cluster, you can upgrade Kudu packages manually. For instructions, see Upgrade Kudu Using the Command Line.