[
https://issues.apache.org/jira/browse/SLIDER-950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15007687#comment-15007687
]
Gour Saha commented on SLIDER-950:
----------------------------------
[~thomas_liu] the method looks ok, but can you implement the API end to end. At
a high level I think, if there is any information we need to extract from the
slider AM, then we need to hit the AM of every single app in the list. I don't
think we have the option to do it in a single call. So you might have to use
executors and a thread pool of reasonable size to achieve some amount of
parallelization.
However, if there is any information we can get from RM, then we need to ensure
that RM API supports multi get for the info we are looking for.
Here is the 2.7.1 RM API for your reference -
https://hadoop.apache.org/docs/stable/hadoop-yarn/hadoop-yarn-site/ResourceManagerRest.html
So on a second thought implementing getStatus in a single API for multiple apps
might be a challenge. But I think we should be able to do it for getRegistry
which is SLIDER-951.
So let's create an end-to-end patch for both these bugs and see if we can trim
down or drop some data and create a lightweight projection of the API. Not all
clients needs all the info that a single app get API provides.
> Implement GetStatus API call for multiple applications
> ------------------------------------------------------
>
> Key: SLIDER-950
> URL: https://issues.apache.org/jira/browse/SLIDER-950
> Project: Slider
> Issue Type: New Feature
> Components: client
> Affects Versions: Slider 0.80
> Reporter: thomas liu
> Assignee: thomas liu
> Fix For: Slider 0.90
>
> Attachments: SLIDER-950-DISCUSSION-1.patch
>
>
> We found it useful to implement an API to allow getting status for multiple
> applications in a cluster. We restrict the applications to a list of names we
> pass into the API
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
