Support Questions

Find answers, ask questions, and share your expertise

start scheduling services one by one

avatar
Expert Contributor

I would know if there is an order to respect when we start services on HDP in Ambari

1 ACCEPTED SOLUTION

avatar
Super Guru

@yassine sihi,

There is a json file (role_command_order.json) which specifies the dependencies of starting/stopping the services.

If there is no dependency then the start/stop of services between hosts will run in parallel. You can find the files by running the command in ambari server node

find /var/lib/ambari-server/resources -iname role_command_order.json

Files inside common-services(/var/lib/ambari-server/resources/common-services) specify the dependency at a service level whereas files inside (/var/lib/ambari-server/resources/stacks) specify overall dependencies at stack level.

Consider this sample line in one of the file

"LIVY_SERVER-START" : ["NAMENODE-START", "DATANODE-START", "APP_TIMELINE_SERVER-START"]

This specifies that livy server start is dependent on namenode, datanode and app timeline server start.

Hope this helps 🙂

Thanks,

Aditya

View solution in original post

1 REPLY 1

avatar
Super Guru

@yassine sihi,

There is a json file (role_command_order.json) which specifies the dependencies of starting/stopping the services.

If there is no dependency then the start/stop of services between hosts will run in parallel. You can find the files by running the command in ambari server node

find /var/lib/ambari-server/resources -iname role_command_order.json

Files inside common-services(/var/lib/ambari-server/resources/common-services) specify the dependency at a service level whereas files inside (/var/lib/ambari-server/resources/stacks) specify overall dependencies at stack level.

Consider this sample line in one of the file

"LIVY_SERVER-START" : ["NAMENODE-START", "DATANODE-START", "APP_TIMELINE_SERVER-START"]

This specifies that livy server start is dependent on namenode, datanode and app timeline server start.

Hope this helps 🙂

Thanks,

Aditya