You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@activemq.apache.org by magic <ra...@gmail.com> on 2020/04/04 14:40:59 UTC
active mq active-active setup
Dear Team,
I need to setup active-active artemis setup so that my client application
will process the transactions round robin fashion and also for load
balancing the setup with zero downtime.
Could you please let me know if this is possible to have active-active
artemis setup and the required configuration to do it.
I am getting the error when I am trying with below configuration
2020-04-04 20:09:27,862 WARN [org.apache.activemq.artemis.core.client]
AMQ212034: There are more than one servers on the network broadcasting the
same node id. You will see this message exactly once (per node) if a node is
restarted, in which case it can be safely ignored. But if it is logged
continuously it means you really do have more than one node on the same
network active concurrently with the same node id. This could occur if you
have a backup node active at the same time as its live node.
nodeID=060869fb-583f-11ea-aa4b-0050568c6934
I am trying with below configuration and I see
Live1 configuration:
<ha-policy>
<live-only>
<scale-down>
<connectors>
<connector-ref>netty-connector</connector-ref>
</connectors>
</scale-down>
</live-only>
</ha-policy>
<connectors>
<connector
name="netty-connector">tcp://10.130.203.40:61616</connector>
</connectors>
<broadcast-groups>
<broadcast-group name="test-broadcast-group">
<local-bind-address>10.130.203.40</local-bind-address>
<local-bind-port>5432</local-bind-port>
<group-address>231.7.7.7</group-address>
<group-port>9876</group-port>
<broadcast-period>100</broadcast-period>
<connector-ref>netty-connector</connector-ref>
</broadcast-group>
</broadcast-groups>
<discovery-groups>
<discovery-group name="test-discovery-group">
<local-bind-address>0.130.203.40</local-bind-address>
<group-address>231.7.7.7</group-address>
<group-port>9876</group-port>
<refresh-timeout>10000</refresh-timeout>
</discovery-group>
</discovery-groups>
<cluster-connections>
<cluster-connection name="test-cluster">
<address>jms,queue.test,test</address>
<connector-ref>netty-connector</connector-ref>
<check-period>1000</check-period>
<connection-ttl>5000</connection-ttl>
<min-large-message-size>50000</min-large-message-size>
<call-timeout>5000</call-timeout>
<retry-interval>500</retry-interval>
<retry-interval-multiplier>1.0</retry-interval-multiplier>
<max-retry-interval>5000</max-retry-interval>
<initial-connect-attempts>-1</initial-connect-attempts>
<reconnect-attempts>-1</reconnect-attempts>
<use-duplicate-detection>true</use-duplicate-detection>
<message-load-balancing>STRICT</message-load-balancing>
<max-hops>1</max-hops>
<confirmation-window-size>20000</confirmation-window-size>
<call-failover-timeout>30000</call-failover-timeout>
<notification-interval>1000</notification-interval>
<notification-attempts>2</notification-attempts>
<discovery-group-ref
discovery-group-name="test-discovery-group"/>
</cluster-connection>
</cluster-connections>
Live2 configuration:
<connectors>
<connector
name="netty-connector">tcp://10.130.203.41:61616</connector>
</connectors>
<broadcast-groups>
<broadcast-group name="test-broadcast-group">
<local-bind-address>10.130.203.41</local-bind-address>
<local-bind-port>5432</local-bind-port>
<group-address>231.7.7.7</group-address>
<group-port>9876</group-port>
<broadcast-period>100</broadcast-period>
<connector-ref>netty-connector</connector-ref>
</broadcast-group>
</broadcast-groups>
<discovery-groups>
<discovery-group name="test-discovery-group">
<local-bind-address></local-bind-address>
<group-address>231.7.7.7</group-address>
<group-port>9876</group-port>
<refresh-timeout>10000</refresh-timeout>
</discovery-group>
</discovery-groups>
<cluster-connections>
<cluster-connection name="test-cluster">
<address>jms,queue.test,test</address>
<connector-ref>netty-connector</connector-ref>
<check-period>1000</check-period>
<connection-ttl>5000</connection-ttl>
<min-large-message-size>50000</min-large-message-size>
<call-timeout>5000</call-timeout>
<retry-interval>500</retry-interval>
<retry-interval-multiplier>1.0</retry-interval-multiplier>
<max-retry-interval>5000</max-retry-interval>
<initial-connect-attempts>-1</initial-connect-attempts>
<reconnect-attempts>-1</reconnect-attempts>
<use-duplicate-detection>true</use-duplicate-detection>
<message-load-balancing>STRICT</message-load-balancing>
<max-hops>1</max-hops>
<confirmation-window-size>20000</confirmation-window-size>
<call-failover-timeout>30000</call-failover-timeout>
<notification-interval>1000</notification-interval>
<notification-attempts>2</notification-attempts>
<discovery-group-ref
discovery-group-name="test-discovery-group"/>
</cluster-connection>
</cluster-connections>
Please let me know if my approach is correct and any more details
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html