Jian He commented on YARN-3999:

Thanks for reviewing the patch. Rohith.
bq. For expire , the new events would trigger which is blocked since dispatcher 
is draining.
ATS events processing happens on a different dispatcher.
bq. Why the end time considering half of the rm-expire interval
No strong reason why it depends on am-rm-expiry. Just want to avoid introducing 
rarely-used config. Anyway, I introduced a new config for this.
bq.  Ther is issue exist for test failures in TestRMAdminService.
I would like to introduce  this fix to trigger jenkins. Otherwise, Too many 
failures. I can't see a clean results.

> RM hangs on draing 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
>         Attachments: YARN-3999.1.patch, YARN-3999.2.patch, YARN-3999.2.patch, 
> YARN-3999.3.patch, YARN-3999.4.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

Reply via email to