Component execution and commands

Run component

Hadoop Eco runs components as OS system services. System services operate components using commands in the format systemctl [start|stop|restart] [service-name].
The following shows how to run components as OS system services in Hadoop Eco.

Example of running component (Zookeeper service)

Action	Command
Start	sudo systemctl start zookeeper
Stop	sudo systemctl stop zookeeper
Restart	sudo systemctl restart zookeeper

Component execution commands

The following are commands for running components.

info

For Trino, coordinator and worker are determined by options, and both run with the same command.

Module	Component	Command
Zookeeper	zookeeper	sudo systemctl start zookeeper
HDFS	namenode	sudo systemctl start namenode
	journalnode	sudo systemctl start journalnode
	zkfc	sudo systemctl start zkfc
	datanode	sudo systemctl start datanode
	secondarynamenode	sudo systemctl start secondarynamenode
Yarn	resource manager	sudo systemctl start resourcemanager
	nodemanager	sudo systemctl start nodemanager
	timelineserver	sudo systemctl start timelineserver
	jobhistoryserver	sudo systemctl start jobhistoryserver
	tez-ui	sudo systemctl start tez-ui
	sparkhistoryserver	sudo systemctl start sparkhistoryserver
HBase	hmaster	sudo systemctl start hmaster
	regionserver	sudo systemctl start regionserver
Trino	coordinator	sudo systemctl start trino
	worker	sudo systemctl start trino
Oozie	oozie	sudo systemctl start oozie
Hue	hue	sudo systemctl start hue
Zeppelin	zeppelin	sudo systemctl start zeppelin
Druid	druid master-query server (coordinator-overlord, broker, router)	sudo systemctl start druid-master-query-server
	druid master-broker server (coordinator-overlord, broker)	sudo systemctl start druid-master-broker-server
	druid data server (historical, middleManager)	sudo systemctl start druid-data-server
Kafka	kafka	sudo systemctl start kafka
Superset	superset	sudo systemctl start superset