Github user wenlong88 commented on the issue:
https://github.com/apache/flink/pull/3599
Hi, I may have described my concern wrongly in the last comment, my concern
is that in yarn it is possible that two application master running at the same
time:
eg: RM launches a AM and then the machine lost connection with RM by some
reason, RM will launch another AM. It is possible that the first AM will be
still running when launching the second AM in some scenario like NM heartbeat
timeout but running.
When it is possible that there are two AM running at the same time, we may
go into a dead lock using the AlwaysLeaderService as follows:
1. the first AM grant leadership
2. the second AM grant leadership
3. the second AM write leader info
4. the first AM write leader info
5. the first AM killed by NM or some cluster monitor tool since RM marked
NM as unavailable.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
