-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
Consumer using assign() does not re-query coordinator after NOT_COORD_FOR_GROUP #2791
Comments
For instance NOT_COORD_FOR_GROUP would not trigger a coordinator query.
For instance NOT_COORD_FOR_GROUP would not trigger a coordinator query.
For instance NOT_COORD_FOR_GROUP would not trigger a coordinator query.
Hi Magnus. Thank you for looking into fixing it. Tell me please your thoughts on me adding a fallback to my consumer to trap _WAIT_COORD (-180) and NOT_COORDINATOR_FOR_GROUP (16) and get the consumer to destroy the old connection handle and create a new one (similar to the work around in #2630)? Do you think it is worth while or that the imminent fix you are working on will make that unnecessary? Do you think that trapping those will lead to unnecessary, expensive and possibly frequent reconnects? |
v1.4.2 with this fix included will be released later this week. |
Thanks @edenhill , sounds great! Though what would you say to me still having the reconnect fallback in case consecutive errors of this form happen? |
The workaround should no longer be needed. |
@edenhill I'm using node-rdkafka version 2.7.4 and got the below error and I'm using consumer assign() & had auto commit flag as true. If I upgrade to 2.9.x version will this issue be fixed automatically ? Like the consumer will rejoin the group automatically with out any work around ? Error: {"severity":4,"fac":"COMMITFAIL","message":"[thrd:main]: Offset commit (cgrp auto commit timer) failed for 0/1 partition(s): mytopic[0]@8747(Broker: Unknown member)"} |
Description
Consumers using the
assign()
API instead of thesubscribe()
API can get into a state where they keep unsuccessfully trying to commit offsets to a broker that is no longer the group coordinator. They stay in this state until they're restarted.This might be related to #2630
How to reproduce
librdkafka client code excerpts:
Sequence of events to reproduce issue:
Checklist
Please provide the following information:
1.3.0
2.2.0
Red Hat Enterprise Linux Server release 7.6 (Maipo)
debug=..
as necessary) from librdkafkalibrdkafka client configuration dump:
Full librdkafka debug logs: https://gist.github.com/mlongob/4ecfe850cbdacc24b53e789be016e371
librdkafka debug logs excerpts:
Broker logs excerpts:
Series of events:
mygroup
mygroup
mygroup
The consumer is able to successfully recover from event (2) but not from event (3)
The text was updated successfully, but these errors were encountered: