[
https://issues.apache.org/jira/browse/FLINK-32046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Peter Vary updated FLINK-32046:
-------------------------------
Description:
If the checkpointing is turned off then the
{{SplitAssignmentTracker.uncheckpointedAssignments}} is never cleared and grows
indefinitely. Eventually leading to OOM.
The only other place which would remove elements from this map is
{{{}getAndRemoveUncheckpointedAssignment{}}}, but it is only for failure
scenarios.
By my understanding this problem exists since the introduction of the new
{{Source}} implementation.
was:
If the checkpointing is turned off then the
{{SplitAssignmentTracker.uncheckpointedAssignments}} is never cleared and grows
indefinitely. Eventually leading to OOM.
The only other place which would remove elements from this map is
{{{}getAndRemoveUncheckpointedAssignment{}}}, but it is only for failure
scenarios.
By my understanding this problem exists since the introduction of the new
source code.
> OOM caused by SplitAssignmentTracker.uncheckpointedAssignments
> --------------------------------------------------------------
>
> Key: FLINK-32046
> URL: https://issues.apache.org/jira/browse/FLINK-32046
> Project: Flink
> Issue Type: Bug
> Components: API / Core
> Reporter: Peter Vary
> Priority: Major
>
> If the checkpointing is turned off then the
> {{SplitAssignmentTracker.uncheckpointedAssignments}} is never cleared and
> grows indefinitely. Eventually leading to OOM.
> The only other place which would remove elements from this map is
> {{{}getAndRemoveUncheckpointedAssignment{}}}, but it is only for failure
> scenarios.
> By my understanding this problem exists since the introduction of the new
> {{Source}} implementation.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
