Github user zentol commented on the issue:
https://github.com/apache/flink/pull/3709
It shouldn't matter for the display in the web-frontend in which data
structure the cached ExecutionGraphs are being held. We are caching the actual
ExecutionGraph that the JobManager works with and not some copy, thus there is
simply no way for the handler to work with outdated data. This implies that the
entire premise of this issue is flawed.
It's more likely some web-related issue like the page not refreshing
automatically or being cached by the browser for an inexplicable long time.
---
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.
---
