Github user tillrohrmann commented on the issue:
https://github.com/apache/flink/pull/2257
It is true that the duplicate RegisterTaskManager messages fix could have
been a separate PR. Since it surfaces as a symptom of the registration problem,
I thought about fixing it in the same PR. The separation should be clear
(TaskManager vs. RM changes).
The reason why I had to change more code than this single line is that the
RM shouldn't interfere with the TaskManager registration to be on the safe
side. As far as I've understood, the RM should tell you about a dying TM but it
should not forbid the registration of a TM at the JM. I think that this
conservative behaviour is more robust wrt the old behaviour and helps us to not
overlook other corner cases.
Furthermore, some of the changes were necessary to make the YARN RM
component more easily testable.
---
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 [email protected] or file a JIRA ticket
with INFRA.
---
