hachikuji commented on PR #12674: URL: https://github.com/apache/kafka/pull/12674#issuecomment-1273652187
> 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. Hmm, perhaps that handling is good enough? In the event that the out of range error was spurious, the follower would soon catch up to the leader. I assume that is the common case unless unclean election is enabled. It does not seem like a big problem if there is a delay finding a genuine out of range case. -- 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]
