Migrating from Packages to Parcels

Minimum Required Role: Cluster Administrator (also provided by Full Administrator)

Managing software distribution using parcels offers many advantages over packages. To migrate from packages to the same version parcel, perform the following steps. To upgrade to a different version, see Upgrading the CDH Cluster.

  1. Download, Distribute, and Activate Parcels
  2. Restart the Cluster and Deploy Client Configuration
  3. Uninstall Packages
  4. Update Applications to Reference Parcel Paths

Download, Distribute, and Activate Parcels

  1. In the Cloudera Manager Admin Console, click the parcel icon in the top navigation bar.
  2. Click Download for the version that matches the CDH or service version of the currently installed packages. If the parcel you want is not shown here—for example, if you want to use a version of CDH that is not the most current version—you can add parcel repositories through the Parcel Configuration Settings page. If your Cloudera Manager Server does not have Internet access, you can obtain the required parcel file(s) and put them into a repository. See Configuring a Local Parcel Repository for more details.
  3. When the download has completed, click Distribute for the version you downloaded.
  4. When the parcel has been distributed and unpacked, the button will change to say Activate.
  5. Click Activate.

Restart the Cluster and Deploy Client Configuration

  1. Restart the cluster:
    1. On the Home > Status tab, click to the right of the cluster name and select Restart.
    2. Click Restart that appears in the next screen to confirm. If you have enabled high availability for HDFS, you can choose Rolling Restart instead to minimize cluster downtime. The Command Details window shows the progress of stopping services.

      When All services successfully started appears, the task is complete and you can close the Command Details window.

    You can optionally perform a rolling restart.
  2. Redeploy client configurations:
    1. On the Home > Status tab, click to the right of the cluster name and select Deploy Client Configuration.
    2. Click Deploy Client Configuration.

Uninstall Packages

  1. If your Hue service uses the embedded SQLite database, back up /var/lib/hue/desktop.db to a location that is not /var/lib/hue because this directory is removed when the packages are removed.
  2. Uninstall the CDH packages on each host:
    • Not including Impala, Kudu, and Search
      Operating System Command
      RHEL 
      sudo yum remove bigtop-utils bigtop-jsvc bigtop-tomcat hue-common sqoop2-client
      SLES 
      sudo zypper remove bigtop-utils bigtop-jsvc bigtop-tomcat hue-common sqoop2-client
      Ubuntu or Debian 
      sudo apt-get purge bigtop-utils bigtop-jsvc bigtop-tomcat hue-common sqoop2-client
    • Including Impala, Kudu, and Search
      Operating System Command
      RHEL 
      sudo yum remove 'bigtop-*' hue-common impala-shell kudu solr-server sqoop2-client hbase-solr-doc avro-libs crunch-doc avro-doc solr-doc
      SLES 
      sudo zypper remove 'bigtop-*' hue-common impala-shell kudu solr-server sqoop2-client hbase-solr-doc avro-libs crunch-doc avro-doc solr-doc
      Ubuntu or Debian 
      sudo apt-get purge 'bigtop-*' hue-common impala-shell kudu solr-server sqoop2-client hbase-solr-doc avro-libs crunch-doc avro-doc solr-doc
  3. Restart all the Cloudera Manager Agents to force an update of the symlinks to point to the newly installed components on each host: 
    sudo service cloudera-scm-agent restart
  4. If your Hue service uses the embedded SQLite database, restore the database you backed up:
    1. Stop the Hue service.
    2. Copy the backup from the temporary location to the newly created Hue database directory, /var/lib/hue.
    3. Start the Hue service.

Update Applications to Reference Parcel Paths

With parcels, the path to the CDH libraries is /opt/cloudera/parcels/CDH/lib instead of the usual /usr/lib. Do not link /usr/lib/ elements to parcel-deployed paths, because the links can cause scripts that distinguish between the two paths to not work. Instead you should update your applications to reference the new library locations.