hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Junping Du (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-667) Data persisted in RM should be versioned
Date Tue, 13 May 2014 13:16:16 GMT

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

Junping Du commented on YARN-667:

Thanks for your comments, [~zjshen]! 
bq. Shall we consider the version of history data as well?
That's good point. We should consider history data, like: ApplicationHistoryData, ApplicationAttemptHistoryData,
ContainerHistoryData, etc. could be variable in future and make them proper versioned. In
addition, any changes on format (i.e. APPLICATION_PREFIX, etc.) and path of history file (root+appID
for now) could be very challenge on rolling upgrade (also seen as incompatible change I think).
[~zjshen], do you have sense on how possibility it could happen in 2.X as you are currently
work on ATS?

> Data persisted in RM should be versioned
> ----------------------------------------
>                 Key: YARN-667
>                 URL: https://issues.apache.org/jira/browse/YARN-667
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>    Affects Versions: 2.0.4-alpha
>            Reporter: Siddharth Seth
>            Assignee: Junping Du
> Includes data persisted for RM restart, NodeManager directory structure and the Aggregated
Log Format.

This message was sent by Atlassian JIRA

View raw message