You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "clebert suconic (JIRA)" <ji...@apache.org> on 2014/11/12 22:04:33 UTC

[jira] [Commented] (ACTIVEMQ6-23) Improve connection load balancing

    [ https://issues.apache.org/jira/browse/ACTIVEMQ6-23?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14208681#comment-14208681 ] 

clebert suconic commented on ACTIVEMQ6-23:
------------------------------------------

There could/should be a proxy component only responsible fore transferring load and doing some loading.

I believe there is a similar component on activemq5 doing that.

> 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)