[ https://issues.apache.org/jira/browse/YARN-5547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15490429#comment-15490429 ]
Ajith S commented on YARN-5547: ------------------------------- As per offline discussion with [~Naganarasimha Garla] and [~varun_saxena] for {{If the old software could consult a table in the database that lists what keys are ignorable then it can fail for any unrecognized key that isn't in that list and safely ignore ones that are}} we can add a suffix for the keys if they are ignoreable so that even lower version will know if keys can be skipped safely > NMLeveldbStateStore should be more tolerant of unknown keys > ----------------------------------------------------------- > > Key: YARN-5547 > URL: https://issues.apache.org/jira/browse/YARN-5547 > Project: Hadoop YARN > Issue Type: Improvement > Components: nodemanager > Affects Versions: 2.6.0 > Reporter: Jason Lowe > Assignee: Ajith S > Attachments: YARN-5547.01.patch > > > Whenever new keys are added to the NM state store it will break rolling > downgrades because the code will throw if it encounters an unrecognized key. > If instead it skipped unrecognized keys it could be simpler to continue > supporting rolling downgrades. We need to define the semantics of > unrecognized keys when containers and apps are cleaned up, e.g.: we may want > to delete all keys underneath an app or container directory when it is being > removed from the state store to prevent leaking unrecognized keys. -- 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