hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "MENG DING (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (YARN-4138) Roll back container resource allocation after resource increase token expires
Date Wed, 03 Feb 2016 18:59:39 GMT

     [ https://issues.apache.org/jira/browse/YARN-4138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

MENG DING updated YARN-4138:
----------------------------
    Attachment: YARN-4138.5.patch

Hi, [~jianhe]

bq. After step 6, rmContainer.getLastConfirmedResource() will return 3G, when the expire event
gets triggered, won't it reset it back to 3G?

No, it won't reset it back to 3G. rmContainer.getLastConfirmedResource() will not return 3G
after step 6, it is still 1G. We only confirm resource when NM reported resource is the same
as RM resource. In this test case, NM reported resource is 3G, but RM allocated resource is
6G, so 3G is NOT confirmed. This issues was discussed in this thread a while ago: https://issues.apache.org/jira/browse/YARN-4138?focusedCommentId=14737229&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14737229

bq. I think RMContainerImpl will not receive EXPIRE event at RUNNING state after this patch
? if so, we can remove this.

You are right, we can remove this. Attaching the latest patch that remove this.


> Roll back container resource allocation after resource increase token expires
> -----------------------------------------------------------------------------
>
>                 Key: YARN-4138
>                 URL: https://issues.apache.org/jira/browse/YARN-4138
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: api, nodemanager, resourcemanager
>            Reporter: MENG DING
>            Assignee: MENG DING
>         Attachments: YARN-4138-YARN-1197.1.patch, YARN-4138-YARN-1197.2.patch, YARN-4138.3.patch,
YARN-4138.4.patch, YARN-4138.5.patch
>
>
> In YARN-1651, after container resource increase token expires, the running container
is killed.
> This ticket will change the behavior such that when a container resource increase token
expires, the resource allocation of the container will be reverted back to the value before
the increase.



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

Mime
View raw message