[
https://issues.apache.org/jira/browse/AMQ-2106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13115250#comment-13115250
]
Joakim Örtbrant commented on AMQ-2106:
--------------------------------------
This feature is very important not only to utilize all consumers after a
consumer crash and recovery but also deliberate shutdown/startup of consumers.
In our case this happens each time we do a new release of our distributed
consumer application. We have consumers spread across multiple servers and
redeploy 1 server at a time to not have any downtime, the end result of this is
that after the release the consumers are no longer evenly distributed across
the servers (last server that was updated does not have any active consumers
and is now a pure backup). A config setting to configure the behaviour and/or
some way to force a reassign at runtime would be much appriciated!
> Allow broker to evenly distribute message groups among consumers
> ----------------------------------------------------------------
>
> Key: AMQ-2106
> URL: https://issues.apache.org/jira/browse/AMQ-2106
> Project: ActiveMQ
> Issue Type: New Feature
> Components: Broker
> Affects Versions: 5.2.0
> Reporter: Dejan Bosanac
> Assignee: Dejan Bosanac
> Fix For: 5.x
>
>
> Currently the broker will not reassign message groups if new consumers
> becomes available (or existing ones are removed). We could allow the broker
> to try reassign the message groups when consumers are added/removed so that
> we have a even distribution among consumers.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
