Start
IMPORTANT
If you installed a monitoring cluster and want to use it with the ADH cluster, start the monitoring cluster first. To do this, run the Start action of the monitoring cluster in the same way as described for the ADH cluster.
|
The Start action starts all the services installed in the ADH cluster, one by one, in the correct order.
To run an action, go to Clusters page, click in the Actions column, and select the action from the drop-down list that appears.
The dialog window of the Start action contains the Apply services configs from ADCM setting that allows you to determine whether configuration options specified in ADCM UI should be applied to ADH services.
Click Run to start the cluster. In the action confirmation window that appears, you can select the Verbose checkbox to see additional execution details.
You can find execution process and result of the action on the Jobs page. On this page you can view action execution details, including verbose Ansible STDOUT/STDERR outputs.
Alternatively, you can use the Start service action of a particular service to manually start only required services. It is necessary to run services in the order shown in the table below.
Number in order | Service name |
---|---|
1 |
Monitoring (if you use the monitoring cluster) |
2 |
Zookeeper |
3 |
MySQL |
4 |
HDFS |
5 |
YARN |
6 |
HBase |
7 |
Hive |
8 |
Spark |
9 |
Flink |
10 |
Solr |
11 |
Sqoop |
12 |
Airflow |
Most ADH services require the following running services:
-
Zookeeper
-
HDFS
-
YARN