[
https://issues.apache.org/jira/browse/SLIDER-947?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14969372#comment-14969372
]
Steve Loughran commented on SLIDER-947:
---------------------------------------
The AM only gets nodemap updates from the RM; it can't get the full map from
RM. The YARN client can, and we could do it before launching the AM, but after
an AM restart that map could very out of date.
Proposed: we start a YARN client in the AM to issue the relevant call. On a
long-lived secure cluster, the keytab will handle this, we just need to make
sure that the delegation tokens built up for short-lived clusters include one
for the RM.
> build node map from yarn update reports; serve via REST/IPC
> -----------------------------------------------------------
>
> Key: SLIDER-947
> URL: https://issues.apache.org/jira/browse/SLIDER-947
> Project: Slider
> Issue Type: Sub-task
> Components: appmaster, Web & REST
> Affects Versions: Slider 0.90
> Reporter: Steve Loughran
> Assignee: Steve Loughran
> Fix For: Slider 2.0.0
>
> Original Estimate: 2h
> Remaining Estimate: 2h
>
> Before doing any anti-affinity allocation, update the state of the cluster
> from the RM events, and make it visible via the IPC and REST APIs.
> That way, we and the tests can see what is going on
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
