Apache Kudu Installation and Upgrade

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.

Platform Requirements

Before you proceed with installation or upgrade, review Platform Requirements.

Downloading and Installing Kudu

Minimum Required Role: Cluster Administrator

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 Cloudera Installation Guide.

Starting CDH 6.3.3, you must have an Enterprise Support Subscription to access archive.cloudera.com.

If you want support for Kudu's NVM (non-volatile memory) block cache, then you must install the memkind library by running one of the following commands for the corresponding platform:
  • RHEL/CentOS: 
    sudo yum install memkind
  • Ubuntu or Debian: 
    sudo apt-get install libmemkind0
  • SLES: 
    sudo zypper install memkind
If the memkind package provided with the Linux distribution is too old, you can build and install it from source by using the following commands:
  • RHEL/CentOS: 
    sudo yum install numactl-libs numactl-devel
    git clone https://github.com/memkind/memkind.git
    cd memkind
    ./build.sh --prefix=/usr
    sudo yum remove memkind
    sudo make install
    sudo ldconfig
  • Ubuntu or Debian: 
    sudo apt-get install libnuma1 libnuma-dev
    git clone https://github.com/memkind/memkind.git
    cd memkind
    ./build.sh --prefix=/usr
    sudo apt-get remove memkind
    sudo make install
    sudo ldconfig
  • SLES: 
    sudo zypper install numactl-libs numactl-devel
    git clone https://github.com/memkind/memkind.git
    cd memkind
    ./build.sh --prefix=/usr
    sudo zypper remove memkind
    sudo make install
    sudo ldconfig

Upgrading Kudu

Before you proceed with an upgrade, review the Install and Upgrade Notes.

On a managed cluster,
  • 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 the CDH Cluster.
  • 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 the CDH Cluster.