[FLINK-18578] Add rejecting checkpoint logic in source

• Type: New Feature
• Status: Open
• Priority: Minor
• Resolution: Unresolved
• Fix Version/s: 2.0.0
• Component/s: Connectors / Common, Runtime / Checkpointing
• Labels: auto-deprioritized-major auto-unassigned
• Assignee: Unassigned
• Reporter: Qingsheng Ren
• Created: 13/Jul/20 07:00
• Updated: 10/Jul/24 06:57

Description

Under some database's change data capture (CDC) case, the process is usually divided into two phases: snapshotting phase (lock captured tables and scan all records in them) and log streaming phase (read all changes starting from the moment of locking tables) in order to build a complete view of captured tables. The first snapshotting phase should be atomic so we have to give up all records created in snapshotting phase if any failure happen, because contents in captured tables might have changed during recovery. And checkpointing within snapshotting phase is meaningless too.

As a result, we need to add a new feature in the source to reject checkpoint if the source is currently within an atomic operation or some other processes that cannot do a checkpoint currently. This rejection should not be treated as a failure that could lead to failure of the entire job. 
 

Issue Links

• is related to: FLINK-32514 FLIP-309: Support using larger checkpointing interval when source is processing backlog