hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Varun Saxena (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-6323) Rolling upgrade/config change is broken on timeline v2.
Date Wed, 09 Aug 2017 13:43:00 GMT

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

Varun Saxena commented on YARN-6323:

bq.  However YARN-6736 is planning to write into both v1 and v2 timelines during upgrade.
I think we should make use of it during rolling upgrade so that RM will publish data into
v1 and v2. 
Makes sense to me if we are doing rolling upgrade from v1 to v2. This way transition would
be seamless as the user can switch back to only v2 once he is sure that all the applications
running at the time of previous switchover (when both v1 and v2 were configured) have completed.
And he can trust the data in v2 completely from a particular application onwards.
This would also be useful for those who want to try out v2 before they make a final decision
to switch over to v2.

> Rolling upgrade/config change is broken on timeline v2. 
> --------------------------------------------------------
>                 Key: YARN-6323
>                 URL: https://issues.apache.org/jira/browse/YARN-6323
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: timelineserver
>            Reporter: Li Lu
>            Assignee: Vrushali C
>              Labels: yarn-5355-merge-blocker
>         Attachments: YARN-6323.001.patch
> Found this issue when deploying on real clusters. If there are apps running when we enable
timeline v2 (with work preserving restart enabled), node managers will fail to start due to
missing app context data. We should probably assign some default names to these "left over"
apps. I believe it's suboptimal to let users clean up the whole cluster before enabling timeline

This message was sent by Atlassian JIRA

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

View raw message