rob-9 opened a new issue, #1174: URL: https://github.com/apache/flink-agents/issues/1174
### Search before asking - [x] I searched in the [issues](https://github.com/apache/flink-agents/issues) and found nothing similar. ### Description A durable call result can be written to Fluss before a checkpoint while its action is still pending. The checkpoint records the bucket end offsets, and recovery starts from those offsets, potentially skipping the saved result and running the call again. Recovery should include saved results still needed by pending actions, even when written before the checkpoint. This is the Fluss equivalent of #1158. #1161 fixes the Kafka implementation. Flagged in #1161. ### How to reproduce 1. Persist a durable call result to Fluss, then leave its action pending (for example, suspended on a later async call). 2. Take a checkpoint. 3. Fail and restore from that checkpoint. 4. Resume the action and check whether the external call runs again. Expected: reuse the saved result without repeating the external call. ### Version and environment Reproduced against an embedded Fluss 0.9.0-incubating cluster using the source at #1161 head `14ee1feb57f9b8b02335d222c237e8523709a36f`. A test executed `RunnerContextImpl.durableExecute`, persisted its successful result in an incomplete action state, captured the recovery marker, and rebuilt a fresh Fluss store. The saved result was missing, and replay through a fresh durable context executed the callable again: expected call count `1`, actual `2`. As a control, rebuilding from a marker captured before the write recovered the same result and kept the call count at `1`. This verifies the Fluss store and durable-call paths; a full Flink checkpoint/failover test has not been run. ### 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]
