THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
No special upgrade path is necessary, and this change should be transparent to the user – they will just see that cooperative rebalancing is enabled.
...
- Some cooperative-sticky related defects might not freed before V3.0
→ We've marked an important defect KAFKA-12896 defects as blocker for V3.0, ex: KAFKA-12896. Please raise any important defect if you found any. - cooperative-sticky assignor is also very new for C/C++ users in librdkafka, so not many in that community have tried incremental cooperative yet. And bugs are still recently being worked out there too.
→ Client I checked this library and found currently only 1 cooperative-sticky related bug open, which is good (10 bugs are fixed). Anyway, I think the clients can always change the assignor to other assignors if there are still bugs in the library.