Starting, Stopping, and Restarting Services
Minimum Required Role: Operator (also provided by Configurator, Cluster Administrator, Full Administrator)
Starting and Stopping Services
It's 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.
Starting a Service on All Hosts
- On the tab, click to the right of the service name and select Start.
- Click Start in the next screen to confirm. When you see a Finished status, the service has started.
The order in which to start services is:
- Cloudera Management Service
- ZooKeeper
- HDFS
- Solr
- Flume
- HBase
- Key-Value Store Indexer
- MapReduce or YARN
- Hive
- Impala
- Oozie
- Sqoop
- Hue
Stopping a Service on All Hosts
- On the tab, click to the right of the service name and select Stop.
- Click Stop in the next screen to confirm. When you see a Finished status, the service has stopped.
The order in which to stop services is:
- Hue
- Sqoop
- Oozie
- Impala
- Hive
- MapReduce or YARN
- Key-Value Store Indexer
- HBase
- Flume
- Solr
- HDFS
- ZooKeeper
- Cloudera Management Service
Restarting a Service
- On the tab, click to the right of the service name and select Restart.
- Click Start on the next screen to confirm. When you see a Finished status, the service has restarted.
To restart all services, use the restart cluster action.