You are viewing a plain text version of this content. The canonical link for it is here.

Posted to yarn-issues@hadoop.apache.org by "Sunil G (JIRA)" <ji...@apache.org> on 2015/10/14 19:53:05 UTC

[jira] [Commented] (YARN-3224) Notify AM with containers (on decommissioning node) could be preempted after timeout.

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

Sunil G commented on YARN-3224:
-------------------------------

Hi [~djp]
Could you please help to check this. I have now implemented this patch without updating the preemption timeout to RM. The dependent JIRA is YARN-3784 looks gone stale. Could you please help to advise how we can proceed here. May be I feel we can get this in w/o updating preemption timeout. And once that ticket gets in, we can try making the update for DECOMMISION scenario. Kindly advice.

> Notify AM with containers (on decommissioning node) could be preempted after timeout.
> -------------------------------------------------------------------------------------
>
>                 Key: YARN-3224
>                 URL: https://issues.apache.org/jira/browse/YARN-3224
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>            Reporter: Junping Du
>            Assignee: Sunil G
>         Attachments: 0001-YARN-3224.patch, 0002-YARN-3224.patch
>
>
> We should leverage YARN preemption framework to notify AM that some containers will be preempted after a timeout.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)