[
https://issues.apache.org/jira/browse/YARN-6105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15834116#comment-15834116
]
Varun Saxena edited comment on YARN-6105 at 1/23/17 9:26 AM:
-------------------------------------------------------------
If we do it once a day or every few hours. Some clusters may not be available
immediately if we are relying on this endpoint to first list the clusters.
So, feasible approach entirely depends on use case and the impact its likely to
have on the system if we do a put on a specific event (say app created event).
As discussed in meetup the other day, I guess for Cloud use case, we can
probably write to ATSv2 using a single cluster ID. We do not necessarily need
to track ephemeral clusters which come up and go away. The ephemeral cluster ID
can be probably stored as info. Ephemeral clusters come up and go away so often
that such cluster IDs' are unlikely to make much sense I guess.
was (Author: varun_saxena):
If we do it once a day or every few hours. Some clusters may not be available
immediately if we are relying on this endpoint to first list the clusters.
So, feasible approach entirely depends on use case and the impact its likely to
have on the system if we do a put on a specific even (say app created event).
As discussed in meetup the other day, I guess for Cloud use case, we can
probably write to ATSv2 using a single cluster ID. We do not necessarily need
to track ephemeral clusters which come up and go away. The ephemeral cluster ID
can be probably stored as info. Ephemeral clusters come up and go away so often
that such cluster IDs' are unlikely to make much sense I guess.
> 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
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
