[ 
https://issues.apache.org/jira/browse/YARN-2001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14048333#comment-14048333
 ] 

Vinod Kumar Vavilapalli commented on YARN-2001:
-----------------------------------------------

+1 for the general idea. I suppose you will implement the node-threshold 
separately?

There are a lot of reasons why it makes sense for scheduler to pause for a 
while. Mind adding some of them here and to the config documentation? 
Insufficient state etc.. Are there more issues?

It'd be great to add some tests too.

> Threshold for RM to accept requests from AM after failover
> ----------------------------------------------------------
>
>                 Key: YARN-2001
>                 URL: https://issues.apache.org/jira/browse/YARN-2001
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: resourcemanager
>            Reporter: Jian He
>            Assignee: Jian He
>         Attachments: YARN-2001.1.patch
>
>
> After failover, RM may require a certain threshold to determine whether it’s 
> safe to make scheduling decisions and start accepting new container requests 
> from AMs. The threshold could be a certain amount of nodes. i.e. RM waits 
> until a certain amount of nodes joining before accepting new container 
> requests.  Or it could simply be a timeout, only after the timeout RM accepts 
> new requests. 
> NMs joined after the threshold can be treated as new NMs and instructed to 
> kill all its containers.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to