[
https://issues.apache.org/jira/browse/SLIDER-1197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15868557#comment-15868557
]
Billie Rinaldi commented on SLIDER-1197:
----------------------------------------
[~gsaha], instead of modifying ProviderAppState and storing an instance of the
RM client there, I would suggest creating a wrapper class called something like
ResourceInformationGetter or RMClientAccessForAppState. This class would have a
private variable which is set to the RM client and would have one getter method
that calls amRmClientAsync.getAvailableResources and returns
ResourceInformation. An instance of the wrapper class can be constructed in
SliderAppMaster and passed in AppState's constructor, and then AppState can
call the getter method in AppState.getApplicationLivenessInformation.
> Provide information on pending allocations, and last allocation time, yarn
> mem available
> ----------------------------------------------------------------------------------------
>
> Key: SLIDER-1197
> URL: https://issues.apache.org/jira/browse/SLIDER-1197
> Project: Slider
> Issue Type: Sub-task
> Components: appmaster, client
> Reporter: Siddharth Seth
> Priority: Critical
> Fix For: Slider 1.0.0
>
> Attachments: SLIDER-1197.01.patch
>
>
> This helps with debugging misconfigured apps - where the cluster does not
> have adequate capacity to launch the app
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
