You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Gary Yao (JIRA)" <ji...@apache.org> on 2017/12/20 16:38:00 UTC

[jira] [Updated] (FLINK-8300) Make JobExecutionResult accessible from JobMaster

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

Gary Yao updated FLINK-8300:
----------------------------
    Description: In order to serve the {{JobExecutionResults}} we have to cache them in the {{JobMaster}} after the Job has finished. The cache should have a configurable size and should periodically clean up stale entries in order to avoid memory leaks.  (was: In order to serve the {{JobExecutionResults}} we have to cache them in the {{Dispatcher}} after the {{JobManagerRunner}} has finished. The cache should have a configurable size and should periodically clean up stale entries in order to avoid memory leaks.)

> Make JobExecutionResult accessible from JobMaster
> -------------------------------------------------
>
>                 Key: FLINK-8300
>                 URL: https://issues.apache.org/jira/browse/FLINK-8300
>             Project: Flink
>          Issue Type: Sub-task
>          Components: Distributed Coordination
>    Affects Versions: 1.5.0
>            Reporter: Gary Yao
>            Assignee: Gary Yao
>            Priority: Blocker
>              Labels: flip-6
>             Fix For: 1.5.0
>
>
> In order to serve the {{JobExecutionResults}} we have to cache them in the {{JobMaster}} after the Job has finished. The cache should have a configurable size and should periodically clean up stale entries in order to avoid memory leaks.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)