ijuma commented on PR #12674: URL: https://github.com/apache/kafka/pull/12674#issuecomment-1273482277
Wasn't the 4th option: 4. Return `OFFSET_NOT_AVAILABLE` instead of `OFFSET_OUT_OF_RANGE` if the leader epoch is not provided? > librdkafka does not handle OFFSET_NOT_AVAILABLE well, unfortunately. It only retries the fetch request with a small backoff when it receives it but it does not refresh its metadata so the client would likely not rediscover the correct leader. Two things: 1. We could change librdkafka to refresh its metadata and backport the fix to older versions. 2. How long does librdkafka retry for before giving up? -- 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]
