GitHub user WangTaoTheTonic opened a pull request:
https://github.com/apache/flink/pull/3709
[FLINK-6295]use LoadingCache instead of WeakHashMap to lower latency
Now in ExecutionGraphHolder, which is used in many handlers, we use a
WeakHashMap to cache ExecutionGraph(s), which is only sensitive to garbage
collection.
The latency is too high when JVM do GC rarely, which will make status of
jobs or its tasks unmatched with the real ones. (WE once observed that the web
still shows tasks cancelled/failed, after the actual states of tasks coming
back to normal for **30+ mins,** until a gc happened)
LoadingCache is a common used cache implementation from guava lib, we can
use its time based eviction to lower latency of status update.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/WangTaoTheTonic/flink FLINK-6295
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/flink/pull/3709.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #3709
----
commit d76ced06242623d150f9ad09205e2b92f910c1a1
Author: WangTaoTheTonic <wangtao...@huawei.com>
Date: 2017-04-11T11:48:52Z
use LoadingCache instead of WeakHashMap to lower latency
----
---
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.
---
