[
https://issues.apache.org/jira/browse/ARTEMIS-293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14988039#comment-14988039
]
ASF GitHub Bot commented on ARTEMIS-293:
----------------------------------------
GitHub user jbertram opened a pull request:
https://github.com/apache/activemq-artemis/pull/230
ARTEMIS-293 rebalance inflow on topology change
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/jbertram/activemq-artemis ARTEMIS-293
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/activemq-artemis/pull/230.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #230
----
commit 538fc99594ea748463c0693216c3e3ecc470375c
Author: jbertram <[email protected]>
Date: 2015-10-30T16:20:06Z
ARTEMIS-293 rebalance inflow on topology change
----
> Rebalance JCA RA inflow connections when cluster topology changes
> -----------------------------------------------------------------
>
> Key: ARTEMIS-293
> URL: https://issues.apache.org/jira/browse/ARTEMIS-293
> Project: ActiveMQ Artemis
> Issue Type: New Feature
> Affects Versions: 1.1.0
> Reporter: Justin Bertram
> Assignee: Justin Bertram
> Fix For: 1.1.1
>
>
> The inflow connections for an MDB (or other JCA inflow component) are
> typically long-lived. This is normally a good thing. However, when MDBs are
> consuming messages from a remote cluster and the topology of that cluster
> changes (i.e. a node is added to increase capacity or removed for
> maintenance) the inflow connections don't react in an efficient way. The RA
> should detect topology changes and re-balance the inflow connections across
> the new topology.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
