[
https://issues.apache.org/jira/browse/YARN-3999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vinod Kumar Vavilapalli updated YARN-3999:
------------------------------------------
Fix Version/s: 2.6.1
Pulled this into 2.6.1.
Had to fix a couple of minor merge conflicts. Dropped changes to
TestAsyncDispatcher.java and TestRMAppLogAggregationStatus.java which don't
exist in 2.6.1.
Ran compilation and TestAppManager, TestResourceManager, TestRMAppTransitions,
TestRMAppAttemptTransitions, TestUtils, TestFifoScheduler before the push.
> RM hangs on draining events
> ---------------------------
>
> Key: YARN-3999
> URL: https://issues.apache.org/jira/browse/YARN-3999
> Project: Hadoop YARN
> Issue Type: Bug
> Reporter: Jian He
> Assignee: Jian He
> Labels: 2.6.1-candidate
> Fix For: 2.6.1, 2.7.2
>
> Attachments: YARN-3999-branch-2.7.patch, YARN-3999.1.patch,
> YARN-3999.2.patch, YARN-3999.2.patch, YARN-3999.3.patch, YARN-3999.4.patch,
> YARN-3999.5.patch, YARN-3999.patch, YARN-3999.patch
>
>
> If external systems like ATS, or ZK becomes very slow, draining all the
> events take a lot of time. If this time becomes larger than 10 mins, all
> applications will expire. Fixes include:
> 1. add a timeout and stop the dispatcher even if not all events are drained.
> 2. Move ATS service out from RM active service so that RM doesn't need to
> wait for ATS to flush the events when transitioning to standby.
> 3. Stop client-facing services (ClientRMService etc.) first so that clients
> get fast notification that RM is stopping/transitioning.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
