Introduce batchDeliveryTimeout in client to expire batches that have been stuck for a long time
- Dominant language
- Java
- Stars
- 2.1k
- Forks
- 625
- Avg merge
- 3d 14h
- Merged PRs (30d)
- 97
Description
### Search before asking
- [x] I searched in the [issues](https://github.com/alibaba/fluss/issues) and found nothing similar.
### Motivation
Introduce batchDeliveryTimeout in client to expire batches that have been stuck for a long time. The purpose of this approach is to enable our `Flink job` to recover the write operation by restarting the client via failover. Otherwise, the client may not be able to recover itself, especially when an unrecoverable out-of-order issue occurs due to the server going down unexpectedly.
### Solution
_No response_
### Anything else?
_No response_
### Willingness to contribute
- [x] I'm willing to submit a PR!
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.