mfyuce commented on PR #3525: URL: https://github.com/apache/iggy/pull/3525#issuecomment-4770179177
Update: changed recovery strategy from `first()` to `last()`. Investigated whether `PollingStrategy::first()` would work (it should map to `first_segment.start_offset` on the server, giving the first *available* message with no data skip). However, `PollingKind::First` consistently returns `InvalidOffset(0)` over the TCP binary protocol even when offset 0 is demonstrably valid (the same topic returns offset 0 correctly via the HTTP API). Root cause of the TCP/HTTP discrepancy is TBD. Using `last()` instead: it always succeeds since the most recent message is always in an active segment, breaks the infinite error loop, and gets data flowing. The cost is skipping history that was buffered in Iggy but never consumed. Will open a separate investigation for the `first()` TCP issue. -- 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]
