ravithejatech714-create commented on issue #17637: URL: https://github.com/apache/iceberg/issues/17637#issuecomment-5462937779
The duplicate-coordinator behavior itself clearly belongs in Iceberg. The recovery question afterward is what caught our attention: how do you establish the affected Kafka offsets/range, validate what should be replayed, and recover it without broadly reprocessing unrelated traffic? That's the operator-side recovery workflow we're building around with ReplayGuard. How did you determine the affected source scope in this incident? https://replayguard.in/ -- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
