Github user StephanEwen commented on the issue:
https://github.com/apache/flink/pull/3709
@WangTaoTheTonic I think the big source of confusion is the following: The
cache does not cache any status. It really duplicates the pointer to the life
`ExecutionGraph` object (the `AccessExecutionGraph` and the `ExecutionGraph`
are the same here, the names are an artifact of an earlier approach to create a
History Server).
The only case that is problematic is the case where there are multiple
execution graphs, which happens upon leader change.
Another way to fix this would have been to remove the graph from the cache
whenever leader status is lost.
---
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.
---
