[
https://issues.apache.org/jira/browse/FLINK-5065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-5065:
----------------------------------
Labels: auto-deprioritized-major stale-minor (was:
auto-deprioritized-major)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help
the community manage its development. I see this issues has been marked as
Minor but is unassigned and neither itself nor its Sub-Tasks have been updated
for 180 days. I have gone ahead and marked it "stale-minor". If this ticket is
still Minor, please either assign yourself or give an update. Afterwards,
please remove the label or in 7 days the issue will be deprioritized.
> Resource leaks in case of lost checkpoint messages
> --------------------------------------------------
>
> Key: FLINK-5065
> URL: https://issues.apache.org/jira/browse/FLINK-5065
> Project: Flink
> Issue Type: Bug
> Components: Runtime / Checkpointing
> Affects Versions: 1.1.3, 1.2.0
> Reporter: Till Rohrmann
> Priority: Minor
> Labels: auto-deprioritized-major, stale-minor
>
> In case of lost checkpoint messages ({{AbstractCheckpointMessage}}) there
> won't be a clean up of the contained state handle done. This can happen in
> case of a JM crash if the TM had just sent a checkpoint message to the JM.
> Upon recovery, the JM won't notice that there was a checkpoint message which
> it had to handle.
> One way to mitigate the problem is to let the TM expect a response from the
> JM and if the JM failed to respond in time, to discard the state handle of
> the checkpoint message. Moreover, the JM could register in a fault tolerant
> store that it started a pending checkpoint. The entry should contain enough
> information (e.g. path for {{FileSystemStateBackend}}) to clean up a pending
> checkpoint with potentially lost checkpoint messages upon recovery of the JM.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
