[
https://issues.apache.org/jira/browse/YARN-6095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15826652#comment-15826652
]
Joep Rottinghuis commented on YARN-6095:
----------------------------------------
Just to make sure we capture part of the discussion at the end of YARN-5378:
For a cloud environment, clusters may be ephemeral and come and go relatively
quickly. For that use-case it is desirable to enumerate clusters. I think that
is still a little different than this specific jira, which would take an app ID
and return the list of clusters that this app ID occurred on. Note that in the
vast majority of cases this would return only 1 cluster (or none I suppose).
The use-case of enumerating clusters should use useful without _any_ arguments.
That can happen in two ways: either strongly write this for every app, which
means that we keep inserting / overwriting, or process this after the fact in
the back-end. In either case, that should be a separate jira from this one
imho, unless I mis-understood the discussion on YARN-5378. cc [~rohithsharma]
[~varun_saxena] [~sunilg]
> create a REST API that returns the clusters for a given app id
> --------------------------------------------------------------
>
> Key: YARN-6095
> URL: https://issues.apache.org/jira/browse/YARN-6095
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: timelineserver
> Reporter: Sangjin Lee
>
> It would be good to have a timeline service REST endpoint that can return the
> list of clusters for a given app id. This becomes possible after YARN-5378 is
> in.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
