Static membership = cooperative-sticky

[syepes]

Since kafka 2.3 it has been possible to use static membership across multiple group generations.
If a consumer goes down, a rebalance does not occur right away allowing for the crashed instance to pick up the same partitions when its back up again.

KIP-345

"partition.assignment.strategy" = "cooperative-sticky",

Is this consumer feature currently supported?

[ghost]

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.

[lizthegrey]

Dupe of #1858

[lavoiesl]

The linked KIP-345 is about static membership, but AFAICT, "partition.assignment.strategy" = "cooperative-sticky" is about KIP-341, which is implemented in #1416.

[dnwe]

Yep, so to summarise.

KIP-341 Sticky Assignor was implemented under #1416 and is available since v1.24.0
KIP-345 Static Membership was implemented under #2230 and is available since v1.34.0
KIP-429 Incremental/Cooperative Rebalance Protocol has a work-in-progress PR under #2608 and will hopefully be available in the next release.

I'll close this issue as believe to have already been fixed, and if KIP-429 is desired by the OP then they can follow along at #2608