[FLINK-4437] Lock evasion around lastTriggeredCheckpoint may lead to lost updates to related fields

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.2.0
• Assignee: Unassigned
• Reporter: Ted Yu
• Created: 20/Aug/16 00:19
• Updated: 25/Aug/16 17:07
• Resolved: 25/Aug/16 16:14

Description

In CheckpointCoordinator#triggerCheckpoint():

        // make sure the minimum interval between checkpoints has passed
        if (lastTriggeredCheckpoint + minPauseBetweenCheckpoints > timestamp) {

If two threads evaluate 'lastTriggeredCheckpoint + minPauseBetweenCheckpoints > timestamp' in close proximity before lastTriggeredCheckpoint is updated, the two threads may have an inconsistent view of "lastTriggeredCheckpoint" and updates to fields correlated with "lastTriggeredCheckpoint" may be lost.

Issue Links

• links to: GitHub Pull Request #2409