slfan1989 opened a new pull request, #5672:
URL: https://github.com/apache/hadoop/pull/5672
<!--
Thanks for sending a pull request!
1. If this is your first time, please read our contributor guidelines:
https://cwiki.apache.org/confluence/display/HADOOP/How+To+Contribute
2. Make sure your PR title starts with JIRA issue id, e.g.,
'HADOOP-17799. Your PR title ...'.
-->
### Description of PR
JIRA: YARN-7720. Race condition between second app attempt and UAM timeout
when first attempt node is down.
In Federation, multiple attempts of an application share the same UAM in
each secondary sub-cluster. When first attempt fails, we reply on the fact that
secondary RM won't kill the existing UAM before the AM heartbeat timeout
(default at 10 min). When second attempt comes up in the home sub-cluster, it
will pick up the UAM token from Yarn Registry and resume the UAM heartbeat to
secondary RMs.
The default heartbeat timeout for NM and AM are both 10 mins. The problem is
that when the first attempt node goes down or out of connection, only after 10
mins will the home RM mark the first attempt as failed, and then schedule the
2nd attempt in some other node. By then the UAMs in secondaries are already
timing out, and they might not survive until the second attempt comes up.
### How was this patch tested?
### For code changes:
- [ ] Does the title or this PR starts with the corresponding JIRA issue id
(e.g. 'HADOOP-17799. Your PR title ...')?
- [ ] Object storage: have the integration tests been executed and the
endpoint declared according to the connector-specific documentation?
- [ ] If adding new dependencies to the code, are these dependencies
licensed in a way that is compatible for inclusion under [ASF
2.0](http://www.apache.org/legal/resolved.html#category-a)?
- [ ] If applicable, have you updated the `LICENSE`, `LICENSE-binary`,
`NOTICE-binary` files?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
