Naganarasimha G R commented on YARN-3784:

Thanks for considering [~sunilg],
May be if i am informed with the usage of the preemption timeout then i could 
understand better.
IIUC if its for to take better decision,  then assume  a scenario such that 
AM's heartbeat interval is 3 seconds and the preemption timeout is 5 seconds, 
and assume just after a am heartbeat  container was targeted to be preempted 
then in the next hearbeat that is after 3 seconds it will be informed that a 
container will be timed out in 5 seconds instead of 2 seconds which i feel is 
of little help or might even lead to wrong decisions!. Hence suggested 
timestamp instead of just the timeout value. Thoughts? 
Correct me if i am wrong !

> Indicate preemption timout along with the list of containers to AM 
> (preemption message)
> ---------------------------------------------------------------------------------------
>                 Key: YARN-3784
>                 URL: https://issues.apache.org/jira/browse/YARN-3784
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: resourcemanager
>            Reporter: Sunil G
>            Assignee: Sunil G
>         Attachments: 0001-YARN-3784.patch, 0002-YARN-3784.patch, 
> 0003-YARN-3784.patch, 0004-YARN-3784.patch
> Currently during preemption, AM is notified with a list of containers which 
> are marked for preemption. Introducing a timeout duration also along with 
> this container list so that AM can know how much time it will get to do a 
> graceful shutdown to its containers (assuming one of preemption policy is 
> loaded in AM).
> This will help in decommissioning NM scenarios, where NM will be 
> decommissioned after a timeout (also killing containers on it). This timeout 
> will be helpful to indicate AM that those containers can be killed by RM 
> forcefully after the timeout.

This message was sent by Atlassian JIRA

Reply via email to