[
https://issues.apache.org/jira/browse/YARN-6142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16213458#comment-16213458
]
Ray Chiang commented on YARN-6142:
----------------------------------
Minor issues found by JACC.
YARN-2696
- CapacityScheduler#getQueueComparator() split into partitioned/nonparititoned
comparator
YARN-3139
- Removed synchronized from CapacityScheduler#getContainerTokenSecretManager()
- Removed synchronized from CapacityScheduler#getRMContext()
- Removed synchronized from CapacityScheduler#setRMContext()
YARN-3413
- YarnClient#getClusterNodeLabels() changed return type
YARN-3866
- Major refactor in Public APIs for AM-RM for handling container resizing.
- Change went into both 2.8.0 and 3.0.0.
YARN-3873
- CapacityScheduler#getApplicationComparator() removed
YARN-4593
- AbstractService#getConfig() removed synchronized
YARN-5077
- Removed SchedulingPolicy#checkIfAMResourceUsageOverLimit()
YARN-5221
- AllocateRequest / AllocateResponse has methods changed from Public/Stable to
Public/Unstable
YARN-5713
- Update jackson affects TimelineUtils#dumpTimelineRecordtoJSON()
> 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.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
