Github user zentol commented on the issue:
https://github.com/apache/flink/pull/3709
That this happens when HA is enabled is a really important detail; finally
figured out what happens.
Here's roughly what going on:
* EG A is cached by EGHolder for ID_A
* ZK goes down
* JM revokes leadership, throws out all jobs, specifically EG A stored
under ID_A
* ZK starts up again
* (in your case the same) JM gets leadership back
* JM recovers jobs, which means creating a new EG B, the ID of which is
ID_A again
When a new request hits the EGHolder cache for ID_A there's still the old
EG cached. That old EG will remain there until the GC kicks in, from which
point on the new EG is used.
---
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.
---
