Search before asking
Fluss version
main (development)
Please describe the bug 🐞
Currently, the synchronization of fluss highWatermark involves first updating the leader and then updating the follower in the next round. Log recovery also depends on the highWatermark in the leader's local checkpoint cache to determine whether to truncate data. However, this approach poses a significant risk of data loss as the follower become leader, but the HW of follower lower than leader, it may cause a data truncate.
Solution
No response
Are you willing to submit a PR?