[
https://issues.apache.org/jira/browse/YARN-5375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15422698#comment-15422698
]
sandflee commented on YARN-5375:
--------------------------------
1, replace rmStateStore#AsyncDispatcher with DrainDispatcher, yes the code is
not clean, welcome suggestions!
2, set DrainDispacher#isDrain default value to true, and sleep a while if not
drained to reduce cpu usage.
3, not invoke setDrainEventsOnStop in RMStateStore#DrainDispatcher creation ,
for DrainDispacher will take 300s to stop if enabled setDrainEventsOnStop, file
YARN-5526 to track.
> invoke MockRM#drainEvents implicitly in MockRM methods to reduce test failures
> ------------------------------------------------------------------------------
>
> Key: YARN-5375
> URL: https://issues.apache.org/jira/browse/YARN-5375
> Project: Hadoop YARN
> Issue Type: Improvement
> Reporter: sandflee
> Assignee: sandflee
> Attachments: YARN-5375.01.patch, YARN-5375.03.patch,
> YARN-5375.04.patch, YARN-5375.05.patch, YARN-5375.06.patch
>
>
> seen many test failures related to RMApp/RMAppattempt comes to some state but
> some event are not processed in rm event queue or scheduler event queue,
> cause test failure, seems we could implicitly invokes drainEvents(should also
> drain sheduler event) in some mockRM method like waitForState
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
