Skip to content

Administration of CSDs

Jump to bottom
adar edited this page Mar 5, 2014 · 8 revisions

Cloudera Manager does not fully support dynamic installation of CSDs. Because of this, installing a CSD requires restarting Cloudera Manager.

Installing

  1. Copy the CSD jar to the local repository location. This location is configurable but the default is: /opt/cloudera/csd
  2. Restart Cloudera Manager
  3. Restart all Management Services

Uninstalling

  1. Make sure all services of the CSD service type are stopped and deleted.
  2. Remove the CSD jar from the local repository.
  3. Restart Cloudera Manager
  4. Restart all Management Services.

Note: Although there is a developer shortcut to installing/uninstalling CSDs, this is the only way that Cloudera recommends our customers administer CSDs. Documentation can be found here.

Placeholder Service Handlers

Cloudera Manager has both services and service handlers. A service is a specific instance of a service type and is persisted in the CM database. There can be multiple services for the same service type. A service handler, on the other hand, is stateless and provides the metadata for the service type - commands to run, how to start/stop, and configuration files. A CSD in essence is a service handler that is provided externally through a jar file. For example the SPARK-1.0.jar CSD provides the service handler for the SPARK service type.

Since built-in service handlers like HDFS, are part of the Cloudera Manager binary, they are always present. CSDs on the other hand are all read from disk on startup and stored in memory. If a service exists in the database but there isn't a corresponding CSD on disk on startup, then Cloudera Manager won't know what to do with that service. To address this, Cloudera Manager uses placeholder service handlers.

A placeholder service handler is added to Cloudera Manager if, on startup, it detects there are services in its database without a corresponding CSD. A placeholder service handler provides very limited functionality to the service. A user can only stop the service and delete it. In addition, the service type is no longer available in the wizards. Other situations that can cause placeholders to be created are:

  • the CSD has a validation error and cannot be loaded
  • the CSD is missing
  • an incompatible CSD is added (generation change)

When this happens, the CSD needs to be re-added for functionality to be restored.

Clone this wiki locally