Bikas Saha commented on YARN-3025:

The AM is expected to maintain its own state. However, this could be part of 
the initial sync with the RM when the AM connects to the RM, it could provide 
list of known running containers (which the AM could connect to) etc. However, 
the RM probably does not persist this information after RM restart. So it may 
not be able to provide this information if both the RM and AM restart, leading 
to inconsistent response based on whether one or both have restarted before 

> Provide API for retrieving blacklisted nodes
> --------------------------------------------
>                 Key: YARN-3025
>                 URL: https://issues.apache.org/jira/browse/YARN-3025
>             Project: Hadoop YARN
>          Issue Type: Improvement
>            Reporter: Ted Yu
> We have the following method which updates blacklist:
> {code}
>   public synchronized void updateBlacklist(List<String> blacklistAdditions,
>       List<String> blacklistRemovals) {
> {code}
> Upon AM failover, there should be an API which returns the blacklisted nodes 
> so that the new AM can make consistent decisions.
> The new API can be:
> {code}
>   public synchronized List<String> getBlacklistedNodes()
> {code}

This message was sent by Atlassian JIRA

Reply via email to