You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2018/01/05 08:21:00 UTC
[jira] [Commented] (FLINK-8234) Cache JobExecutionResult from
finished JobManagerRunners
[ https://issues.apache.org/jira/browse/FLINK-8234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16312685#comment-16312685 ]
ASF GitHub Bot commented on FLINK-8234:
---------------------------------------
Github user GJL commented on a diff in the pull request:
https://github.com/apache/flink/pull/5184#discussion_r159826471
--- Diff: flink-runtime/src/main/java/org/apache/flink/runtime/jobmaster/JobMaster.java ---
@@ -936,17 +936,19 @@ private void jobStatusChanged(
final JobID jobID = executionGraph.getJobID();
--- End diff --
Variables declared too early
> Cache JobExecutionResult from finished JobManagerRunners
> --------------------------------------------------------
>
> Key: FLINK-8234
> URL: https://issues.apache.org/jira/browse/FLINK-8234
> Project: Flink
> Issue Type: Sub-task
> Components: Distributed Coordination
> Affects Versions: 1.5.0
> Reporter: Till Rohrmann
> 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 {{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 exhaustion.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)