-
Notifications
You must be signed in to change notification settings - Fork 577
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
Issues with using group instance id with librdkafka #3842
Comments
We've seen the same issue using the Python |
Hi @BalazsHoranyi and @chris-kimberley Redpanda doesn't currently support static group membership which is why you are seeing the errors. Disabling use of group instance id should help until we have support for this feature. |
ah boom. static assignment. makes sense. |
Ah. Do we have an idea for when this would be supported? It's pretty important for our use-case. |
@vsaraswat - we should add this to the compat work @chris-kimberley if you subscribe to this tix it will notify you when we add |
This is a duplicate of #1335 |
landed in dev. |
Version & Environment
Redpanda version: (use
rpk version
):Latest Helm release (21.1.6)
Please also give versions of other components:
kubectl version
):Bringing this conversation over from slack: https://redpandacommunity.slack.com/archives/C01AJDUT88N/p1643398053651669
It appears that librdkafka receives the wrong Kafka API version when it joins the group. This causes unexpected behavior when trying to use group instance IDs.
Minimal example to reproduce:
The text was updated successfully, but these errors were encountered: