diff --git a/docs/user-manual/en/message-grouping.md b/docs/user-manual/en/message-grouping.md index fd82b5f9fc..b53c3a689a 100644 --- a/docs/user-manual/en/message-grouping.md +++ b/docs/user-manual/en/message-grouping.md @@ -98,6 +98,51 @@ producer.send(message); This then closes the message group so if another message is sent in the future with the same message group ID it will be reassigned to a new consumer. +#### Rebalancing Message Groups + +Sometimes after new consumers are added you can find that if you have long lived groups, that they have no groups assigned, and thus are not being utilised, this is because the long lived groups will already be assigned to existing consumers. + +It is possibly to rebalance the groups. + +***note*** during the split moment of reset, a message to the original associated consumer could be in flight at the same time, a new message for the same group is dispatched to the new associated consumer. + +##### Manually + +via the management API or managment console by invoking `resetAllGroups` + +##### Automatically + +By setting `group-rebalance` to `true` at the queue level, every time a consumer is added it will trigger a rebalance/reset of the groups. + +```xml +
+