This is the documentation for Cloudera 5.2.x.
Documentation for other versions is available at Cloudera Documentation.

Migrating from Packages to Parcels

Required Role:

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 CDH and Managed Services Using Cloudera Manager.

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

Download, Distribute, and Activate Parcels

  1. In the Cloudera Manager Admin Console, click the Parcels indicator in the top navigation bar ( or ).
  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:
    • CDH 4
      • CDH - http://archive.cloudera.com/cdh4/parcels/
      • Impala - http://archive.cloudera.com/impala/parcels/
      • Search http://archive.cloudera.com/search/parcels/
      • Spark - http://archive.cloudera.com/spark/parcels/
      • GPL Extras - http://archive.cloudera.com/gplextras/parcels/
    • CDH 5 - Impala, Spark, and Search are included in the CDH parcel.
      • CDH - http://archive.cloudera.com/cdh5/parcels/
      • GPL Extras - http://archive.cloudera.com/gplextras5/parcels/
    • Other services
      • Accumulo - http://archive.cloudera.com/accumulo/parcels/
      • Sqoop connectors - http://archive.cloudera.com/sqoop-connectors/parcels/
    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 Creating and Using a 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 page, click to the right of the cluster name and select Restart.
    2. Click Restart that appears in the next screen to confirm. 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 page, click to the right of the cluster name and select Deploy Client Configuration.
    2. Click Deploy Client Configuration.

Uninstall Packages

  1. Uninstall the CDH packages on each host:
    • Not including Impala 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 and Search
      Operating System Command
      RHEL
      $ sudo yum remove 'bigtop-*' hue-common impala-shell solr-server sqoop2-client
      SLES
      $ sudo zypper remove 'bigtop-*' hue-common impala-shell solr-server sqoop2-client
      Ubuntu or Debian
      $ sudo apt-get purge 'bigtop-*' hue-common impala-shell solr-server sqoop2-client
  2. 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

Restart Cloudera Manager Agents

Restart all the Cloudera Manager Agents to force an update of the symlinks to point to the newly installed components. On each host run:
$ sudo service cloudera-scm-agent restart

Update Applications to Reference Parcel Paths

With parcel software distribution, the path to the CDH libraries is /opt/cloudera/parcels/CDH/lib instead of the usual /usr/lib. You should not link /usr/lib/ elements to parcel deployed paths, as such links may confuse scripts that distinguish between the two paths. Instead you should update your applications to reference the new library locations.