Sephiroth1024 opened a new issue, #10442: URL: https://github.com/apache/seatunnel/issues/10442
### Search before asking - [x] I had searched in the [issues](https://github.com/apache/seatunnel/issues?q=is%3Aissue+label%3A%22bug%22) and found no similar issues. ### What happened When we perform a checkpoint, a counter called `pendingCounter` will increase one. At the end of `CheckpointCoordinator#startTriggerPendingCheckpoint`. <img width="446" height="76" alt="Image" src="https://github.com/user-attachments/assets/a0d6f8b1-c334-4f09-9f34-1e4c4f774f7e"; /> But once it failed, for example, operation timeout (the stack shows as below). ``` CheckpointCoordinator#startTriggerPendingCheckpoint -> CheckpointCoordinator#triggerCheckpoint -> CheckpointManager#sendOperationToMemberNode -> JobMaster#queryTaskGroupAddress (It will access an IMap and may cost a lot. For example, the GetOperation is routed to a partition that has had many operations in its OperationQueue already.) ``` It will never perform a checkpoint again because the `pendingCounter` is 1 and when we perform the checkpoint next time, the code in the red box will be true and it will always be true. <img width="1328" height="1040" alt="Image" src="https://github.com/user-attachments/assets/441e89ef-a8cf-438a-b645-a2428fc2fbe5"; /> So I was wondering if we need to reset `pendingCounter` to 0 when an exception occurs while performing a checkpoint. ### SeaTunnel Version 2.3.12 ### SeaTunnel Config ```conf // ``` ### Running Command ```shell // ``` ### Error Exception ```log // ``` ### Zeta or Flink or Spark Version _No response_ ### Java or Scala Version _No response_ ### Screenshots _No response_ ### Are you willing to submit PR? - [x] Yes I am willing to submit a PR! ### Code of Conduct - [x] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct) -- 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]
