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 "Jason Lowe (JIRA)" <ji...@apache.org> on 2016/09/09 16:25:21 UTC
[jira] [Commented] (YARN-5633) Update Container Version in
NMStateStore only if Resources have changed
[ https://issues.apache.org/jira/browse/YARN-5633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15477490#comment-15477490 ]
Jason Lowe commented on YARN-5633:
----------------------------------
This looks closely related to YARN-5630, although the patch in YARN-5630 doesn't adjust the schema version when the version key needs to be written. Maybe it needs to do so?
> 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
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org