[
https://issues.apache.org/jira/browse/SLIDER-768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14295147#comment-14295147
]
Steve Loughran commented on SLIDER-768:
---------------------------------------
Seems a good idea. Given how we tend to spin & poll in our tests, we could
migrate to it internally too.
# I can add it to an extended component instance data structure
# I can publish it in the forthcoming REST API (SLIDER-151)
It seems to me that you'd benefit from knowing
# a simple yes/no for entire set of apps
# percentage
# summary number of actual & requested
We can do the same for every component (the summaries are there; the boolean
and percentage would be new)
How about I do these for 0.70; we could think about some improvements later (I
could imagine a URL in the rest API which would return an HTTP error code until
the cluster/component type was ready...this would make spinning awaiting a
final state easier)
> API to indicate when all component instances are launched
> ---------------------------------------------------------
>
> Key: SLIDER-768
> URL: https://issues.apache.org/jira/browse/SLIDER-768
> Project: Slider
> Issue Type: Improvement
> Components: appmaster
> Affects Versions: Slider 0.50, Slider 0.60
> Reporter: Lee Yang
> Priority: Minor
>
> Currently, we are querying the Slider AppMaster's "componentinstancedata" API
> in order to get the list of containers/hosts/ports of components launched by
> Slider.
> When launching a large number of components, this API can report back with an
> incomplete list of containers/hosts/ports. Currently, we have to compare
> this list with the number of requested components.
> Ideally, we would like to have some indication of "all components started"
> (either in a separate API, or as part of this existing api).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
