Open chickensoup opened 3 years ago
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 master 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.
I just want to bump this issue from closing. Cooperative rebalance support would be very useful to work with different deployment kinds.
Definitely would also help our issues at Honeycomb where we've had to stop and start all workers at once rather than rolling restart to update
Now Apache Kafka 3.0 has used CooperativeStickyAssignor
as default assignor instead of RangeAssignor
. It seems Sarama has fallen far behind it. It is much more efficient in CooperativeStickyAssignor
.
Still waiting for it!
I believe this issue is referring to https://cwiki.apache.org/confluence/display/KAFKA/KIP-341%3A+Update+Sticky+Assignor%27s+User+Data+Protocol ? That feature was added https://github.com/Shopify/sarama/pull/1416, so I believe this can be closed?
Thanks to @napallday we have a work-in-progress implementation of the incremental cooperate rebalance protocol. If you'd like to test out the changes they are available under PR https://github.com/IBM/sarama/pull/2608
any ETA for this feature ?
Kafka supports consumer incremental cooperative rebalance protocal starting from version 2.4.0, and I'm wondering is there any plan for Sarama client to support this protocol?
KIP-429