You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Hari Sekhon (JIRA)" <ji...@apache.org> on 2018/06/19 11:41:00 UTC

[jira] [Updated] (AMBARI-24144) Ambari API add rack info to HDFS service DATANODE component fields

     [ https://issues.apache.org/jira/browse/AMBARI-24144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Hari Sekhon updated AMBARI-24144:
---------------------------------
    Summary: Ambari API add rack info to HDFS service DATANODE component fields  (was: Ambari API add rack info to HDFS service component fields)

> Ambari API add rack info to HDFS service DATANODE component fields
> ------------------------------------------------------------------
>
>                 Key: AMBARI-24144
>                 URL: https://issues.apache.org/jira/browse/AMBARI-24144
>             Project: Ambari
>          Issue Type: Improvement
>          Components: ambari-server
>    Affects Versions: 2.6.0
>         Environment: HDP 2.6
>            Reporter: Hari Sekhon
>            Priority: Minor
>
> Improvement Request to add rack information to the HDFS service DATANODE components endpoint:
> [https://github.com/apache/ambari/blob/trunk/ambari-server/docs/api/v1/components-component.md]
> I know rack info can be obtained from the hosts API but that is not limited to datanodes, it returns all nodes including edge nodes.
> I wrote [check_ambari_cluster_hdfs_rack_resilience.py|https://github.com/HariSekhon/nagios-plugins/blob/master/check_ambari_cluster_hdfs_rack_resilience.py] Nagios Plugin against that API but it might be better if it didn't enforce this against even edge nodes as there is no datanode running so it's not really relevant, and the alternative is less efficient multiple calls to the API.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)