[
https://issues.apache.org/jira/browse/YARN-6142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15852009#comment-15852009
]
Andrew Wang commented on YARN-6142:
-----------------------------------
I want to highlight a possible YARN issue that [~mackrorysd] found while
working on HDFS-11096. We haven't gotten a response from a YARN person and it
affects 2.8:
{quote}
For YARN (CC Karthik Kambatla), the field nodeLabels in several structures in
yarn_protos changed from string to a custom type, and memory in ResourceProto
change from int32 to int64 (not sure if it's the case in protobuf, but that may
not be incompatible?)
{quote}
[~sunilg] / [~wangda], could you help check this as you worked on YARN-3583
where this change was made? I didn't see a compatibility discussion on that
JIRA.
> Support rolling upgrade between 2.x and 3.x
> -------------------------------------------
>
> Key: YARN-6142
> URL: https://issues.apache.org/jira/browse/YARN-6142
> Project: Hadoop YARN
> Issue Type: Task
> Components: rolling upgrade
> Affects Versions: 3.0.0-alpha2
> Reporter: Andrew Wang
> Assignee: Ray Chiang
> Priority: Blocker
>
> Counterpart JIRA to HDFS-11096. We need to:
> * examine YARN and MR's JACC report for binary and source incompatibilities
> * run the [PB
> differ|https://issues.apache.org/jira/browse/HDFS-11096?focusedCommentId=15816405&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15816405]
> that Sean wrote for HDFS-11096 for the YARN PBs.
> * sanity test some rolling upgrades between 2.x and 3.x. Ideally these are
> automated and something we can run upstream.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
