hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ajith S (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-5547) NMLeveldbStateStore should be more tolerant of unknown keys
Date Mon, 23 Jan 2017 12:02:26 GMT

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

Ajith S commented on YARN-5547:
-------------------------------

[~jlowe] thanks for the comments
I have updated the patch {without storing killed state + checkstyle issues}

> 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, YARN-5547.02.patch, YARN-5547.03.patch, YARN-5547.04.patch,
YARN-5547.05.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-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org


Mime
View raw message