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-6736) Consider writing to both ats v1 & v2 from RM for smoother upgrades
Date Thu, 10 Aug 2017 11:46:00 GMT

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

Varun Saxena commented on YARN-6736:
------------------------------------

Infact, clash of v1 and v2 configurations would be a problem for our internal cluster manager
as well. But we can possibly handle this internally.
The intention initially was to reuse as much of v1 configurations as possible instead of introducing
new ones as we would eventually replace v1.

> Consider writing to both ats v1 & v2 from RM for smoother upgrades
> ------------------------------------------------------------------
>
>                 Key: YARN-6736
>                 URL: https://issues.apache.org/jira/browse/YARN-6736
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: timelineserver
>            Reporter: Vrushali C
>            Assignee: Rohith Sharma K S
>         Attachments: YARN-6736-YARN-5355.001.patch
>
>
> When the cluster is being upgraded from atsv1 to v2, it may be good to have a brief time
period during which RM writes to both atsv1 and v2. This will help frameworks like Tez migrate
more smoothly. 



--
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


Mime
View raw message