You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Sushil Ks (JIRA)" <ji...@apache.org> on 2019/02/01 06:00:05 UTC

[jira] [Assigned] (YARN-6105) Support for new REST end point /clusterids

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

Sushil Ks reassigned YARN-6105:
-------------------------------

    Assignee: Sushil Ks

> Support for new REST end point /clusterids
> ------------------------------------------
>
>                 Key: YARN-6105
>                 URL: https://issues.apache.org/jira/browse/YARN-6105
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: timelineserver
>            Reporter: Rohith Sharma K S
>            Assignee: Sushil Ks
>            Priority: Major
>
> As discussed in YARN-5378 and YARN-6095, it is required to have */clusterids* that returns list of clusterids that back end has is useful. 
> Use case : In cloud, clusters are arbitrarily spin up and destroyed. Each cluster has its own clusterId which UI never knows about it. To all those newly spin up cluster, same ATS server has been used. And sam web UI has been used. Admin can select the clusterId and navigate to any pages. So, it is worth to list ClusterId's from ATS



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

---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org