Starting CDH Services Using the Command Line
You need to start and stop services in the right order to make sure everything starts or stops cleanly.
START services in this order:
Order | Service | Comments | For instructions and more information |
---|---|---|---|
1 |
ZooKeeper |
Cloudera recommends starting ZooKeeper before starting HDFS; this is a requirement in a high-availability (HA) deployment. In any case, always start ZooKeeper before HBase. |
Installing the ZooKeeper Server Package and Starting ZooKeeper on a Single Server; Installing ZooKeeper in a Production Environment; Deploying HDFS High Availability; Configuring High Availability for the JobTracker (MRv1) |
2 |
HDFS |
Start HDFS before all other services except ZooKeeper. If you are using HA, see the CDH 5 High Availability Guide for instructions. |
|
3 |
HttpFS |
|
|
4a |
MRv1 |
Start MapReduce before Hive or Oozie. Do not start MRv1 if YARN is running. |
Deploying MapReduce v1 (MRv1) on a Cluster; Configuring High Availability for the JobTracker (MRv1) |
4b |
YARN |
Start YARN before Hive or Oozie. Do not start YARN if MRv1 is running. |
|
5 |
HBase |
|
Starting and Stopping HBase; Deploying HBase in a Distributed Cluster |
6 |
Hive |
Start the Hive metastore before starting HiveServer2 and the Hive console. |
|
7 |
Oozie |
|
|
8 |
Flume 1.x |
|
|
9 |
Sqoop |
|
|
10 |
Hue |
|
<< Managing CDH Using the Command Line | ©2016 Cloudera, Inc. All rights reserved | Configuring init to Start Hadoop System Services >> |
Terms and Conditions Privacy Policy |