[jira] [Commented] (FLINK-17308) ExecutionGraphCache cachedExecutionGraphs not cleanup cause OOM Bug
[ https://issues.apache.org/jira/browse/FLINK-17308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17093091#comment-17093091 ] Till Rohrmann commented on FLINK-17308: --- It's fine to include this fix with 1.10.2. > ExecutionGraphCache cachedExecutionGraphs not cleanup cause OOM Bug > --- > > Key: FLINK-17308 > URL: https://issues.apache.org/jira/browse/FLINK-17308 > Project: Flink > Issue Type: Bug > Components: Runtime / REST >Affects Versions: 1.9.0, 1.9.1, 1.9.2, 1.10.0 >Reporter: yujunyong >Assignee: Till Rohrmann >Priority: Critical > Labels: pull-request-available > Fix For: 1.11.0, 1.10.2, 1.9.4 > > > class org.apache.flink.runtime.rest.handler.legacy.ExecutionGraphCache will > cache job execution graph in field > "cachedExecutionGraphs" when call method > "getExecutionGraph", but never call it's > cleanup method in flink. it's cause JobManager Out of Memory, When submit a > lot of batch job and fetch these job's info. becasue these operation cache > all these job execution graph and "cleanup" method never called -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (FLINK-17308) ExecutionGraphCache cachedExecutionGraphs not cleanup cause OOM Bug
[ https://issues.apache.org/jira/browse/FLINK-17308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17091144#comment-17091144 ] sunjincheng commented on FLINK-17308: - Reset the fix version as 1.9.3 was released. > ExecutionGraphCache cachedExecutionGraphs not cleanup cause OOM Bug > --- > > Key: FLINK-17308 > URL: https://issues.apache.org/jira/browse/FLINK-17308 > Project: Flink > Issue Type: Bug > Components: Runtime / REST >Affects Versions: 1.9.0, 1.9.1, 1.9.2, 1.10.0 >Reporter: yujunyong >Assignee: Till Rohrmann >Priority: Critical > Labels: pull-request-available > Fix For: 1.10.1, 1.11.0, 1.9.4 > > > class org.apache.flink.runtime.rest.handler.legacy.ExecutionGraphCache will > cache job execution graph in field > "cachedExecutionGraphs" when call method > "getExecutionGraph", but never call it's > cleanup method in flink. it's cause JobManager Out of Memory, When submit a > lot of batch job and fetch these job's info. becasue these operation cache > all these job execution graph and "cleanup" method never called -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (FLINK-17308) ExecutionGraphCache cachedExecutionGraphs not cleanup cause OOM Bug
[ https://issues.apache.org/jira/browse/FLINK-17308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17090350#comment-17090350 ] Till Rohrmann commented on FLINK-17308: --- Thanks for reporting this issue [~yujunyong]. This is indeed a mistake and should be corrected. I will prepare a PR for it. > ExecutionGraphCache cachedExecutionGraphs not cleanup cause OOM Bug > --- > > Key: FLINK-17308 > URL: https://issues.apache.org/jira/browse/FLINK-17308 > Project: Flink > Issue Type: Bug > Components: Runtime / REST >Affects Versions: 1.9.0, 1.9.1, 1.9.2, 1.10.0 >Reporter: yujunyong >Priority: Critical > > class org.apache.flink.runtime.rest.handler.legacy.ExecutionGraphCache will > cache job execution graph in field > "cachedExecutionGraphs" when call method > "getExecutionGraph", but never call it's > cleanup method in flink. it's cause JobManager Out of Memory, When submit a > lot of batch job and fetch these job's info. becasue these operation cache > all these job execution graph and "cleanup" method never called -- This message was sent by Atlassian Jira (v8.3.4#803005)
