activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Scott England-Sullivan (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMQ-3707) Dynamic Failover Client Connection Params Broker Side Attribute
Date Thu, 09 Feb 2012 14:30:00 GMT

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

Scott England-Sullivan commented on AMQ-3707:
---------------------------------------------

I think that idea here is that in a cluster or dynamic failover configuration, the broker
should be setting these values as it could be unique for each broker.  For dynamic failover
the initial failover string used to configure the client is really a bootstrap because it
is most likely not complete.  Therefore the clients should connect and get their configuration
settings per broker.

Otherwise, the assumption is that all brokers are created equal and you may have a broker
in a new environment that has more resources available.  

This would also open the way for weighting brokers in the rebalance.
                
> Dynamic Failover Client Connection Params Broker Side Attribute
> ---------------------------------------------------------------
>
>                 Key: AMQ-3707
>                 URL: https://issues.apache.org/jira/browse/AMQ-3707
>             Project: ActiveMQ
>          Issue Type: New Feature
>          Components: Broker
>            Reporter: Scott England-Sullivan
>             Fix For: 5.6.0
>
>
> Given that dynamic failover allows for the addition and removal of brokers from a list
of available connections at the client, I would suggest that an attribute be made available
on the broker to define what connection options a client should use when connecting to a given
broker.
> Therefore a client with the following list of connections:
> Client connect string
> * failover://(tcp://somebrokerA:61616,tcp://somebrokerB:61616)
> And a broker with the following
> * (NEW) *clusterClientsConnectionParams="useCompression=true"*
> Would result in a client with the following connection list:
> * tcp://somebrokerA:61616?clusterClientsConnectionParams="useCompression=true"
> * tcp://somebrokerB:61616?clusterClientsConnectionParams="useCompression=true"
> And should a new broker be added to the cluster (if this option was set on each broker):
> * tcp://somebrokerA:61616?clusterClientsConnectionParams="useCompression=true"
> * tcp://somebrokerB:61616?clusterClientsConnectionParams="useCompression=true"
> * tcp://somebrokerC:61616?clusterClientsConnectionParams="useCompression=true"
> Thanks,
> Scott ES
> http://fusesource.com

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

        

Mime
View raw message