[FLINK-5285] CancelCheckpointMarker flood when using at least once mode

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.2.0, 1.1.3
• Fix Version/s: 1.2.0, 1.1.4
• Component/s: State Backends, Checkpointing
• Assignee: Till Rohrmann
• Reporter: Till Rohrmann
• Created: 08/Dec/16 10:14
• Updated: 09/Dec/16 16:54
• Resolved: 09/Dec/16 16:54

Description

When using at least once mode (BarrierTracker), then an interleaved arrival of cancellation barriers at the BarrierTracker of two consecutive checkpoints can trigger a flood of CancelCheckpointMarkers.

The following sequence is problematic:

Cancel(1, 0),
Cancel(2, 0),
Cancel(1, 1),
Cancel(2, 1),
Cancel(1, 2),
Cancel(2, 2)

with Cancel(checkpointId, channelId)

Issue Links

• links to: GitHub Pull Request #2963
• links to: GitHub Pull Request #2964