[
https://issues.apache.org/jira/browse/ACTIVEMQ6-23?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Taylor updated ACTIVEMQ6-23:
-
Description: Move the connection load balancing to the server side by
allowing the cluster to decide where a client should connect to on initial
connect, removing the functionality from the client. All the client should need
to know on reconnect or failover is its initial servers id. we can then plumb
in more dynamic load balancing based on queue depth etc. (was: This will be an
integrated gateway with Zoo Keeper.
A Connection ID will set what node is coming, and the gateway will work as a
proxy to the node where the connection is sitting on.)
Summary: Improve connection load balancing (was: Broker Gateway to
massive scale up clients)
> Improve connection load balancing
> -
>
> Key: ACTIVEMQ6-23
> URL: https://issues.apache.org/jira/browse/ACTIVEMQ6-23
> Project: Apache ActiveMQ 6
> Issue Type: New Feature
>Reporter: clebert suconic
> Fix For: 6.1.0
>
>
> Move the connection load balancing to the server side by allowing the cluster
> to decide where a client should connect to on initial connect, removing the
> functionality from the client. All the client should need to know on
> reconnect or failover is its initial servers id. we can then plumb in more
> dynamic load balancing based on queue depth etc.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
