[GitHub] flink issue #3745: [FLINK-6341]Don't let JM fall into infinite loop

[tillrohrmann <gi...@git.apache.org>]

Github user tillrohrmann commented on the issue:

    https://github.com/apache/flink/pull/3745
  
    Thanks for spotting the problem @WangTaoTheTonic. This is important to fix.
    
    I think we cannot solve the problem as you've done it, because you access actor state from outside of the actor's main thread. I think it would be better to introduce a resource manager connection id which we can use to distinguish whether we have to reconnect from a resource manager or whether it is an outdated `ReconnectResourceManager` message. We can do the check then in the handler for the `ReconnectResourceManager` message.


---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---