[
https://issues.apache.org/jira/browse/YARN-3094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vinod Kumar Vavilapalli updated YARN-3094:
------------------------------------------
Fix Version/s: 2.6.1
Pulled this into 2.6.1. Ran compilation and TestAMLivelinessMonitor before the
push. Patch applied cleanly.
> reset timer for liveness monitors after RM recovery
> ---------------------------------------------------
>
> Key: YARN-3094
> URL: https://issues.apache.org/jira/browse/YARN-3094
> Project: Hadoop YARN
> Issue Type: Bug
> Components: resourcemanager
> Affects Versions: 2.6.0
> Reporter: Jun Gong
> Assignee: Jun Gong
> Labels: 2.6.1-candidate
> Fix For: 2.7.0, 2.6.1
>
> Attachments: YARN-3094.2.patch, YARN-3094.3.patch, YARN-3094.4.patch,
> YARN-3094.5.patch, YARN-3094.patch
>
>
> When RM restarts, it will recover RMAppAttempts and registry them to
> AMLivenessMonitor if they are not in final state. AM will time out in RM if
> the recover process takes long time due to some reasons(e.g. too many apps).
> In our system, we found the recover process took about 3 mins, and all AM
> time out.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)