-
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
RoundRobin assignor question #3159
Comments
Huhm, yes, or that we iterate eligible_topic->members instead. |
Good at least we know now were is the issue :) we had like 5 instance subscribing topic 'A' and all 45 partitions assigned to single instance |
Could it lead to infinite loop also if not lucky in first range ( limited by this module ) ? |
Seems like that, yeah. I'll fix it. |
The roundrobin partition assignment strategy could get stuck in an endless loop or generate uneven assignments in case the group members had asymmetric subscriptions (e.g., c1 subscribes to t1,t2 while c2 subscribes to t2,t3).
The roundrobin partition assignment strategy could get stuck in an endless loop or generate uneven assignments in case the group members had asymmetric subscriptions (e.g., c1 subscribes to t1,t2 while c2 subscribes to t2,t3).
@plachor I'll roll a v1.5.3 maintenance release this week |
The roundrobin partition assignment strategy could get stuck in an endless loop or generate uneven assignments in case the group members had asymmetric subscriptions (e.g., c1 subscribes to t1,t2 while c2 subscribes to t2,t3).
Thanks ;) |
v1.5.3 is now released |
The roundrobin partition assignment strategy could get stuck in an endless loop or generate uneven assignments in case the group members had asymmetric subscriptions (e.g., c1 subscribes to t1,t2 while c2 subscribes to t2,t3).
The roundrobin partition assignment strategy could get stuck in an endless loop or generate uneven assignments in case the group members had asymmetric subscriptions (e.g., c1 subscribes to t1,t2 while c2 subscribes to t2,t3).
Hi, I'm experiencing not well balanced partition assignments (with round-robin assignor selected). My issue is that partitions from topic 'A' are not properly distributed among all group members with active subscription to topic 'A'. This happens if in consumer group there are mixed subscriptions like:
I've been looking for an issue on my side without any luck so far. So I checked your implementation on Github and I wonder if on:
https://github.com/edenhill/librdkafka/blob/55995b9afed08dc33a0da0c161507fa429f10322/src/rdkafka_roundrobin_assignor.c#L87-L92
this modulo should not take members count instead? I might been misunderstanding it as I have not opened this code yet in any IDE and it been years since I written any thing in c++.
The text was updated successfully, but these errors were encountered: