Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

sarama consumer client can not return to leader when the client fetch from follower which is outed of isr #2464

Open
mtj075 opened this issue Apr 14, 2023 · 4 comments
Labels
needs-investigation Issues that require followup from maintainers stale/exempt Issues and pull requests that should never be closed as stale

Comments

@mtj075
Copy link

mtj075 commented Apr 14, 2023

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

@mtj075 mtj075 changed the title sarama consumer client can not return to leader when the client fetch from follower sarama consumer client can not return to leader when the client fetch from follower which is outed of isr Apr 20, 2023
@github-actions
Copy link

Thank you for taking the time to raise this issue. However, it has not had any activity on it in the past 90 days and will be closed in 30 days if no updates occur.
Please check if the main branch has already resolved the issue since it was raised. If you believe the issue is still valid and you would like input from the maintainers then please comment to ask for it to be reviewed.

@github-actions github-actions bot added the stale Issues and pull requests without any recent activity label Jul 19, 2023
@mtj075
Copy link
Author

mtj075 commented Jul 19, 2023 via email

@github-actions github-actions bot removed the stale Issues and pull requests without any recent activity label Jul 19, 2023
@github-actions
Copy link

Thank you for taking the time to raise this issue. However, it has not had any activity on it in the past 90 days and will be closed in 30 days if no updates occur.
Please check if the main branch has already resolved the issue since it was raised. If you believe the issue is still valid and you would like input from the maintainers then please comment to ask for it to be reviewed.

@github-actions github-actions bot added the stale Issues and pull requests without any recent activity label Oct 17, 2023
@mtj075
Copy link
Author

mtj075 commented Oct 17, 2023 via email

@github-actions github-actions bot removed the stale Issues and pull requests without any recent activity label Oct 17, 2023
@dnwe dnwe added needs-investigation Issues that require followup from maintainers stale/exempt Issues and pull requests that should never be closed as stale labels Oct 17, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs-investigation Issues that require followup from maintainers stale/exempt Issues and pull requests that should never be closed as stale
Projects
None yet
Development

No branches or pull requests

2 participants