[jira] [Updated] (FLINK-6295) use LoadingCache instead of WeakHashMap to lower latency

["Tao Wang (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/FLINK-6295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tao Wang updated FLINK-6295:
----------------------------

Thanks for the digging. I guess that's the reason :)




-----------------
Regards.
On 04/18/2017 20:34, ASF GitHub Bot (JIRA) wrote:

   [ https://issues.apache.org/jira/browse/FLINK-6295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15972584#comment-15972584 ]

ASF GitHub Bot commented on FLINK-6295:
---------------------------------------

Github user zentol commented on the issue:

   https://github.com/apache/flink/pull/3709
 
   Give a bit time to think of other ways to solve this; we are trying to reduce the usage of guava, let's see if there isn't another way. 30 seconds still seem like a long time to server an old EG.





--
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)