Github user zentol commented on the issue:
https://github.com/apache/flink/pull/3709
@WangTaoTheTonic Because *everyone* uses guava which results again and
again in dependency conflicts.
What do you mean with "how long it should be"? We remove the job from the
cache and that's it. If more request for that job come in nothing will be
returned resulting in the response you get when querying for a non-existing
job, which is an accurate representation of the state of the JobManager. If the
same JM recovers the job then it is no longer in a SUSPENDED state and will be
added to the cache again. If another JM picks the job up the web-ui will be
redirected to that JM and everything's fine.
---
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.
---
