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 "Vrushali C (JIRA)" <ji...@apache.org> on 2017/08/31 23:56:00 UTC

[jira] [Updated] (YARN-5547) NMLeveldbStateStore should be more tolerant of unknown keys

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

Vrushali C updated YARN-5547:
-----------------------------
    Attachment: YARN-5547-branch-2.8.2.001.patch

Uploading patch for branch-2.8.2 . Same patch as branch-2. The affected unit test works on my laptop. Will reopen jira to trigger jenkins. 



> 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
>             Fix For: 2.9.0, 3.0.0-alpha4
>
>         Attachments: YARN-5547.01.patch, YARN-5547.02.patch, YARN-5547.03.patch, YARN-5547.04.patch, YARN-5547.05.branch-2.patch, YARN-5547.05.patch, YARN-5547-branch-2.8.2.001.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.4.14#64029)

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