Github user tillrohrmann commented on the issue:
https://github.com/apache/flink/pull/3745
It is a problem because, the `currentResourceManager` is not volatile.
Thus, you might miss some state changes in the future callback because of a
cached value. Moreover, accessing mutable actor state from a different thread
breaks the actor encapsulation and can lead to subtle race conditions and other
synchronization bugs.
---
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.
---
