Cloudera Docs

Starting a Cloudera Runtime Service on All Hosts

Starting and Stopping Cloudera Runtime services.

Minimum Required Role: Operator (also provided by Configurator, Cluster Administrator, Limited Cluster Administrator , and Full Administrator)

It is important to start and stop services that have dependencies in the correct order. For example, because MapReduce and YARN have a dependency on HDFS, you must start HDFS before starting MapReduce or YARN. The Cloudera Management Service and Hue are the only two services on which no other services depend; although you can start and stop them at anytime, their preferred order is shown in the following procedures. The Cloudera Manager cluster actions start and stop services in the correct order. To start or stop all services in a cluster, follow the instructions in Starting, Stopping, Refreshing, and Restarting a Cluster.

The order in which to start services is:
  1. Cloudera Management Service
  2. ZooKeeper
  3. HDFS
  4. Solr
  5. HBase
  6. Key-Value Store Indexer
  7. MapReduce or YARN
  8. Hive
  9. Impala
  10. Oozie
  11. Sqoop
  12. Hue
  1. In the left menu, click Clusters and select a service.
  2. Click to the right of the service name and select Start.
  3. Click Start in the next screen to confirm.
    When you see a Finished status, the service has started.