View the cluster daemon from Edge node

[#1]

How to view the cluster daemon from Edge node

[#2]

@Mohamed Farook

Can you please elaborate what do you exactly mean by "cluster daemon" ?

And also what do you mean by "Viewing cluster daemon" ?

[#3]

Hi Jay,

Like by running 'jps' we can view all the services running in our cluster. Is that any options are there to view what are the services running in my cluster from my edge node?

[#4]

@Mohamed Farook,

You can check it by running ssh from the edge node .

ssh {hostname} jps

.

-Aditya

[#5]

Hi Aditya,

I dont think this is the correct. Instead of login to edge node and check the services on master/slave hostname. Is there I can install jdk file in my edge node and to check services on master/slave hosts.

[#6]

@Mohamed Farook,

I'm not sure if that is possible.

[#7]

@Mohamed Farook

You can make use fo Ambari API call to findout all the component /service status using a single API call. The API call can be made from any node of the cluster (Evev from Edge Node).

We will see status of component/services like "INSTALLED"/ "STARTED".

Here "INSTALLED" means not running and "STARTED" means running state for the components. For Client conponents like HDFS_CLIENT/HIVE_CLIENT ...etc we will always see "INSTALLED" state.

Example:

# curl -u admin:admin -H "X-Requested-By: ambari" -X GET http://myambariserver.example.com:8080/api/v1/clusters/TestCluster/components?fields=ServiceComponen... | grep -A 2 component_name | awk '{print $NF}' > /tmp/requests_details.txt; sed -e '1,2d' -e s'/--//g'  -e 's/\n//g' -e 's/"//g' -e '/^$/d' /tmp/requests_details.txt | awk 'NR%3{printf "%s ",$0;next;}1' 

Example Output:

STARTED DATANODE, HDFS,
STARTED DATANODE, hdfcluster1.example.com,
STARTED DATANODE, hdfcluster2.example.com,
STARTED DATANODE, hdfcluster3.example.com,
STARTED DATANODE, hdfcluster4.example.com,
STARTED DRPC_SERVER, STORM,
STARTED HBASE_MASTER, hdfcluster4.example.com,
STARTED HBASE_REGIONSERVER, HBASE,
STARTED HBASE_REGIONSERVER, hdfcluster3.example.com,
STARTED HBASE_REGIONSERVER, hdfcluster4.example.com,
STARTED HCAT, HIVE,
STARTED HISTORYSERVER, hdfcluster2.example.com,
STARTED HIVE_CLIENT, HIVE,
STARTED HIVE_METASTORE, hdfcluster3.example.com,
STARTED HIVE_SERVER, HIVE,
STARTED HIVE_SERVER, hdfcluster3.example.com,
STARTED HIVE_SERVER_INTERACTIVE, HIVE,
STARTED HIVE_SERVER_INTERACTIVE, hdfcluster2.example.com,
STARTED HST_AGENT, hdfcluster1.example.com,
STARTED HST_SERVER, hdfcluster1.example.com,
STARTED INFRA_SOLR, hdfcluster4.example.com,
STARTED INFRA_SOLR_CLIENT, AMBARI_INFRA,
STARTED NAMENODE, HDFS,
STARTED NAMENODE, hdfcluster1.example.com,
STARTED NAMENODE, hdfcluster2.example.com,
STARTED RESOURCEMANAGER, hdfcluster2.example.com,
STARTED RESOURCEMANAGER, hdfcluster3.example.com,
STARTED SECONDARY_NAMENODE, HDFS,
.
.

.

In the above API call you will need to make the changes for the following values:

1. TestCluster : Replace this with your own cluster name.

2. admin:admin : Replace this with your own ambari admin username:password.

3. http://myambariserver.example.com:8080 Replace this URL with your own ambari server URL.