[
https://issues.apache.org/jira/browse/FLINK-6295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tao Wang updated FLINK-6295:
----------------------------
I doubt it. EGH is simply a cache, I don't think it should be assigned too
heavy task. Another concern is that not just JM failover affecting status of
tasks.
-----------------
Regards.
On 04/18/2017 21:06, ASF GitHub Bot (JIRA) wrote:
[
https://issues.apache.org/jira/browse/FLINK-6295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15972628#comment-15972628
]
ASF GitHub Bot commented on FLINK-6295:
---------------------------------------
Github user zentol commented on the issue:
https://github.com/apache/flink/pull/3709
Assuming that some JM will be granted leadership and recovers the suspended
jobs, the easiest solution would be to simply check in the EGHolder whether the
cached job is in the SUSPENDED state, and remove it from the cache if it is.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
> use LoadingCache instead of WeakHashMap to lower latency
> --------------------------------------------------------
>
> Key: FLINK-6295
> URL: https://issues.apache.org/jira/browse/FLINK-6295
> Project: Flink
> Issue Type: Bug
> Components: Webfrontend
> Reporter: Tao Wang
> Assignee: Tao Wang
>
> 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.
> LoadingCache is a common used cache implementation from guava lib, we can use
> its time based eviction to lower latency of status update.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
