luoyuxia commented on issue #2648: URL: https://github.com/apache/fluss/issues/2648#issuecomment-3884543475
However, I believe we could consider a method to mitigate this behavior, which was discussed during the initial design phase but not yet implemented. If the Enumerator's heartbeat detects an anomaly in the fenceTieringEpoch, the Enumerator should immediately cancel the current synchronization. This would prevent 'zombie' tiering services from submitting data. Currently, there is a possibility that the service loses connection with the Fluss cluster; however, if a disconnection occurs, getLatestLakeSnapshot will likely fail as well, which would effectively block the submission anyway. Although it may still fail into two jobs tring to commit to lake at the same time, it should resolve most cases. -- 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]
