hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rohith Sharma K S (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-6105) Support for new REST end point /clusterids
Date Mon, 23 Jan 2017 12:11:26 GMT

    [ https://issues.apache.org/jira/browse/YARN-6105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15834350#comment-15834350

Rohith Sharma K S commented on YARN-6105:

In cloud, it is not guaranteed that only one cluster can run at given point of time. I discussed
with cloud team today, constant clusterId or storing it separately as info does not work for
them. Every cluster has its own Id to identify uniqueness. There could be 'N' clusterIds but
those are independent and unique.
So, */clusterids*(with daterange and pagination support) will become more important for shared
services such as YARN web UI, Tez Web UI or Spar Web UI or MR Web UI.

> 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
> 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

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

View raw message