sarama consumer client can not return to leader when the client fetch from follower which is outed of isr #2464
Labels
needs-investigation
Issues that require followup from maintainers
stale/exempt
Issues and pull requests that should never be closed as stale
now, there maybe have a problem, when the sarama client configured the rackid, it will fetch message from the matched follower replica. When the consumer After the replica subscribed by the end falls out of the ISR, the sarama client can not notice. Once the replica falls out of the ISR and does not return to the ISR for a long time, resulting in a backlog of client lag.
I think we can remove followers who have fallen out of ISR from the subscription by listening to ISR on the client side.When the dropped replica returns to the ISR, the leader will return to the corresponding follower for the client to pull data.
What needs to be guaranteed is that the client version > 3.2.3. This version guarantees that the replica returned by the leader is in the isr. https://github.com/apache/kafka/pull/12877/files
The text was updated successfully, but these errors were encountered: