Github user tillrohrmann commented on the issue:
https://github.com/apache/flink/pull/3360
I think adding this safety net makes sense and protects against a corrupted
state.
However, isn't the root cause of the described problem that the
JobMaster-TaskExecutor communication does not tolerate a lost message? Maybe we
should introduce an acknowledge message which signals the correct reception of
the status message. If the response times out we can either retry to send it or
fail.
---
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.
---
