• [DOC] Add a way to handle RebalanceInProgressException thrown in commitSync()/commitAsync with CooperativeStickyAssignor in our document(1).

  I will leave it up to the development team to decide if this ticket task is needed. I have issued this as a report as a just-in-case. Feel free to reject this if not necessary.

• The CooperativeStickyAssignor improves consumer rebalancing efficiency by reducing assignment movement and latency. Currently, RangeAssignor is still the default, but CooperativeStickyAssignor is being considered as the future default. And we provide a way to upgrade consumers to cooperative rebalancing in our document(1).
• However, when using the CooperativeStickyAssignor, if the user commits the offsets manually(enable.auto.commit=false), the user needs to handle RebalanceInProgressException in the Kafka consumer application. if not, during consumer rebalance, RebalanceInProgressException sometimes occurs and any multiple Kafka clients in that consumer group can stop. Then this also leads to duplicate processing of uncommitted messages. I have already received such a report and expect more such reports in the future.
• For details, please refer to the knowledge(2).

(1) 16.7. Upgrading consumers to cooperative rebalancing
https://access.redhat.com/documentation/en-us/red_hat_amq_streams/2.4/html-single/deploying_and_managing_amq_streams_on_openshift/index#proc-upgrading-consumers-streams-cooperative-rebalancing_str

(2) How to handle RebalanceInProgressException thrown in commitSync()/commitAsync with CooperativeStickyAssignor
https://access.redhat.com/solutions/7025439