[
https://issues.apache.org/jira/browse/YARN-5630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15477666#comment-15477666
]
Arun Suresh edited comment on YARN-5630 at 9/9/16 5:33 PM:
-----------------------------------------------------------
Good point...
One option is to
# keep an in memory reference count of : new_NM_store_key - > running
containers are using new NM store keys (we can track this by incrementing if
storeContainerResourceChange is called or storeContainer is called with version
> 0 and decrementing when removeContainer is called for containers whose
version > 0)
# ensure NEW Db version is written only during NM shutdown. If any
new_NM_store_key has a count > 0, increment dbVersion.
was (Author: asuresh):
Good point...
One option is to
# keep an in memory reference count of : new_NM_store_key - > running
containers are using new NM store keys (we can track this by incrementing if
storeContainerResourceChange is called or storeContainer is called with version
> 0 and decrementing when removeContainer is called for containers whose
version > 0)
# ensure Db version is written only during NM shutdown. If any new_NM_store_key
has a count > 0, increment dbVersion.
> NM fails to start after downgrade from 2.8 to 2.7
> -------------------------------------------------
>
> Key: YARN-5630
> URL: https://issues.apache.org/jira/browse/YARN-5630
> Project: Hadoop YARN
> Issue Type: Bug
> Components: nodemanager
> Reporter: Jason Lowe
> Assignee: Jason Lowe
> Priority: Blocker
> Attachments: YARN-5630.001.patch, YARN-5630.002.patch
>
>
> A downgrade from 2.8 to 2.7 causes nodemanagers to fail to start due to an
> unrecognized "version" container key on startup. This breaks downgrades from
> 2.8 to 2.7.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
