You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Justin Bertram (Jira)" <ji...@apache.org> on 2020/03/03 23:20:00 UTC
[jira] [Resolved] (ARTEMIS-2635) Cross network clustering in
Kubernetes not working
[ https://issues.apache.org/jira/browse/ARTEMIS-2635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Justin Bertram resolved ARTEMIS-2635.
-------------------------------------
Resolution: Invalid
Please redirect this question to the [ActiveMQ User mailing list|http://activemq.apache.org/contact/#mailing].
> Cross network clustering in Kubernetes not working
> --------------------------------------------------
>
> Key: ARTEMIS-2635
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2635
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: Broker
> Affects Versions: 2.11.0
> Reporter: Yasin Koyuncu
> Priority: Major
>
> Hi,
>
> I am trying to setup a cross region clustering in 2 separate kubernetes clusters in both regions. I've used a static connector to connect to the remote node on both sides. Although they are able to find each other, they are not forming a cluster. Can anyone explain me why this is not working and how the clustered parties share information for forming clusters?
>
> Here are the configurations:
>
> <connectors>
> <connector name="netty-connector">tcp://10.199.249.236:61616</connector>
> <connector name="remote-connector">tcp://10.199.253.236:61616</connector>
> </connectors>
> ....
> <cluster-connections>
> <cluster-connection name="artemis-cluster">
> <connector-ref>netty-connector</connector-ref>
> <retry-interval>2000</retry-interval>
> <use-duplicate-detection>true</use-duplicate-detection>
> <message-load-balancing>STRICT</message-load-balancing>
> <max-hops>1</max-hops>
> <static-connectors>
> <connector-ref>remote-connector</connector-ref>
> </static-connectors>
> </cluster-connection>
> </cluster-connections>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)