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

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

GitHub user StefanRRichter opened a pull request:

    https://github.com/apache/flink/pull/2837

    [FLINK-5107] Introduced limit for prior execution attempt history

    This PR addresses the problem of JobManager going out of memory for a large 
history of prior execution attempts by pruning the history in FIFO fashion, 
only keeping a limited history size.
    


You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/StefanRRichter/flink limit-prior-executions

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/flink/pull/2837.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 #2837
    
----
commit f9053060fe4d396e9a8917ce8d422b0ebbcc044f
Author: Stefan Richter <s.rich...@data-artisans.com>
Date:   2016-11-18T18:07:56Z

    [FLINK-5107] Introduced limit for prior execution attempt history

----


> Job Manager goes out of memory from long history of prior execution attempts
> ----------------------------------------------------------------------------
>
>                 Key: FLINK-5107
>                 URL: https://issues.apache.org/jira/browse/FLINK-5107
>             Project: Flink
>          Issue Type: Bug
>          Components: JobManager
>            Reporter: Stefan Richter
>            Assignee: Stefan Richter
>
> We have observed that the job manager can run out of memory during long 
> running jobs with many vertexes. Analysis of the heap dump shows, that the 
> ever-growing history of prior execution attempts is the culprit for this 
> problem.
> We should limit this history to a number of n most recent attempts. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to