Github user WangTaoTheTonic commented on the issue:
https://github.com/apache/flink/pull/3709
In my opinion EGHolder is simply a cache which should not be assigned too
complicated task.
If we add the check logic, how long it should be? Will other events
afftects status of tasks? I believe there're more concerns if we added it.
This fix only change internal data structures and decouple with both
JobManager and web frontend.
I am not sure why we are reducing usage of guava, but it sounds not a very
good idea :(
---
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.
---
