hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Arun Suresh (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-5633) Update Container Version in NMStateStore only if Resources have changed
Date Fri, 09 Sep 2016 16:50:22 GMT

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

Arun Suresh commented on YARN-5633:

Marking this as duplicate of YARN-5630.
YARN-5630 also handles the case where the AM requests and receives an increased Resource Container
BEFORE starting the version 0 Container in the NM.

> Update Container Version in NMStateStore only if Resources have changed
> -----------------------------------------------------------------------
>                 Key: YARN-5633
>                 URL: https://issues.apache.org/jira/browse/YARN-5633
>             Project: Hadoop YARN
>          Issue Type: Bug
>            Reporter: Arun Suresh
>            Assignee: Arun Suresh
>         Attachments: YARN-5633-branch-2.8-v1.patch
> YARN-5221 introduced a containerVersion that is stored in the NMStateStore. The version
is stored when
> # the container is first started in the NM
> # when the AM requests the NM to increase the Container resources.
> # when the RM notifies the NM to decrease the Container resources. 
> Unfortunately, this would result in NM not being able to rollback after an upgrade (for
eg. from 2.8 > 2.7).. as noticed by [~jlowe].
> This JIRA proposes to update the version in the NM state store only when 2 and 3 above
occurs, this way, the rollback will be hampered only if the user has used the new feature
(resource increase / decrease)

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org

View raw message