lilei1128 opened a new issue, #9533: URL: https://github.com/apache/paimon/issues/9533
### Search before asking - [x] I searched in the [issues](https://github.com/apache/paimon/issues) and found nothing similar. ### Paimon version paimon 1.3.1 ### Compute Engine Flink 1.16 ### Minimal reproduce step 1. Start a checkpoint-enabled Flink Dedicated Streaming Compact job. 2. Wait until a checkpoint records snapshot N as the next source cursor. 3. Commit newer snapshots. 4. Explicitly trigger snapshot expiration, or use a non-write-only table whose commit path performs expiration, so that snapshot N is removed. 5. Trigger Flink failover and restore from the checkpoint. 6. Observe repeated OutOfRangeException for snapshot N. ### What doesn't meet your expectations? A Flink Dedicated Streaming Compact job can become permanently stuck after recovering from a checkpoint whose next snapshot has already been removed by Paimon snapshot retention. After recovery, the job continues reading the expired snapshot ID and fails with OutOfRangeException. Flink retries the job from the same checkpoint, so every restart uses the same invalid snapshot ID. The job never advances to a valid snapshot and cannot self-recover. Typical error: OutOfRangeException: Snapshot <snapshot-id> does not exist or has expired <img width="1896" height="84" alt="Image" src="https://github.com/user-attachments/assets/e4cd14c4-73b2-41c9-b671-2affdec6869c"; /> ### Anything else? No ### Are you willing to submit a PR? - [x] I'm willing to submit a PR! -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
