Hi!

I’m trying to setup a cross DC setup with one master and two slaves.
Servers are:

Sc0b03 => master
Pr0b03 => slave 1
Sp0b03 => slave 2


The relevante configuration is:

On Master server:

      <connectors>
        <connector name='sc0b03'>tcp://sc0b03:61616</connector>
        <connector name='pr0b03'>tcp://pr0b03:61616</connector>
        <connector name='sp0b03'>tcp://sp0b03:61616</connector>
      </connectors>

      <cluster-user>xxxxxx-user</cluster-user>
      <cluster-password>xXxXxXxXxXxXxXxXxX</cluster-password>

      <ha-policy>
        <replication>
         <master>
            <check-for-live-server>true</check-for-live-server>
          </master>
        </replication>
      </ha-policy>

      <cluster-connections>
        <cluster-connection name="my-cluster">
          <connector-ref>sc0b03</connector-ref>
          <static-connectors>
            <connector-ref>pr0b03</connector-ref>
            <connector-ref>sp0b03</connector-ref>
          </static-connectors>
        </cluster-connection>
      </cluster-connections>


On each Slave (Sp0b03):

      <connectors>
        <connector name='sc0b03'>tcp://sc0b03:61616</connector>
        <connector name='pr0b03'>tcp://pr0b03:61616</connector>
        <connector name='sp0b03'>tcp://sp0b03:61616</connector>
      </connectors>

      <cluster-user>xxxxxx-user</cluster-user>
      <cluster-password>xXxXxXxXxXxXxXxXxX</cluster-password>

      <ha-policy>
        <replication>

        </replication>
      </ha-policy>

      <cluster-connections>
        <cluster-connection name="my-cluster">
          <connector-ref>sp0b03</connector-ref>
          <static-connectors>
            <connector-ref>sc0b03</connector-ref>
            <connector-ref>pr0b03</connector-ref>
          </static-connectors>
        </cluster-connection>
      </cluster-connections>


What happens:

Only one replication (Pr0b03) appears at console:

Cluster Info<http://mq.simfrete.com/console/>
Lives: 1
Backups: 1
HA Policy: Replicated
replicating: true


I’m sure that all servers can touch each other in port “61616” (I’ve used 
telnet to test all of them), and log of servers “Pr0b03” and “Sp0b03” are 
exatcly equals – respected their address diferences.
And I’m sure that if I stop “Pr0b03” then “backups” return to 0.

Relevant startuplog at Sp0b03:

2021-06-04 09:35:12,643 INFO  
[org.apache.activemq.artemis.integration.bootstrap] AMQ101000: Starting 
ActiveMQ Artemis Server
2021-06-04 09:35:12,856 INFO  [org.apache.activemq.artemis.core.server] 
AMQ221000: backup Message Broker is starting with configuration Broker 
Configuration 
(clustered=true,journalDirectory=data/journal,bindingsDirectory=data/bindings,largeMessagesDirectory=data/large-messages,pagingDirectory=data/paging)
2021-06-04 09:35:12,872 INFO  [org.apache.activemq.artemis.core.server] 
AMQ221059: Deleting old data directory /dados/activeMQ/my-cluster/data/journal 
as the max folders is set to 0
2021-06-04 09:35:12,911 INFO  [org.apache.activemq.artemis.core.server] 
AMQ221012: Using AIO Journal
2021-06-04 09:35:13,003 INFO  [org.apache.activemq.artemis.core.server] 
AMQ221057: Global Max Size is being adjusted to 1/2 of the JVM max size (-Xmx). 
being defined as 1.073.741.824
2021-06-04 09:35:13,079 INFO  [org.apache.activemq.artemis.core.server] 
AMQ221043: Protocol module found: [artemis-server]. Adding protocol support 
for: CORE
2021-06-04 09:35:13,081 INFO  [org.apache.activemq.artemis.core.server] 
AMQ221043: Protocol module found: [artemis-amqp-protocol]. Adding protocol 
support for: AMQP
2021-06-04 09:35:13,081 INFO  [org.apache.activemq.artemis.core.server] 
AMQ221043: Protocol module found: [artemis-hornetq-protocol]. Adding protocol 
support for: HORNETQ
2021-06-04 09:35:13,082 INFO  [org.apache.activemq.artemis.core.server] 
AMQ221043: Protocol module found: [artemis-mqtt-protocol]. Adding protocol 
support for: MQTT
2021-06-04 09:35:13,084 INFO  [org.apache.activemq.artemis.core.server] 
AMQ221043: Protocol module found: [artemis-openwire-protocol]. Adding protocol 
support for: OPENWIRE
2021-06-04 09:35:13,085 INFO  [org.apache.activemq.artemis.core.server] 
AMQ221043: Protocol module found: [artemis-stomp-protocol]. Adding protocol 
support for: STOMP
2021-06-04 09:35:13,398 INFO  
[org.apache.activemq.hawtio.branding.PluginContextListener] Initialized 
activemq-branding plugin
2021-06-04 09:35:13,464 INFO  [org.apache.activemq.artemis.core.server] 
AMQ221109: Apache ActiveMQ Artemis Backup Server version 2.17.0 [null] started, 
waiting live to fail before it gets active
2021-06-04 09:35:13,466 INFO  
[org.apache.activemq.hawtio.plugin.PluginContextListener] Initialized 
artemis-plugin plugin
2021-06-04 09:35:13,776 INFO  [io.hawt.HawtioContextListener] Initialising 
hawtio services
2021-06-04 09:35:13,792 INFO  [io.hawt.system.ConfigManager] Configuration will 
be discovered via system properties
2021-06-04 09:35:13,795 INFO  [io.hawt.jmx.JmxTreeWatcher] Welcome to Hawtio 
2.11.0
2021-06-04 09:35:13,802 INFO  [io.hawt.web.auth.AuthenticationConfiguration] 
Starting hawtio authentication filter, JAAS realm: "activemq" authorized 
role(s): "amq" role principal classes: 
"org.apache.activemq.artemis.spi.core.security.jaas.RolePrincipal"
2021-06-04 09:35:13,821 INFO  [io.hawt.web.proxy.ProxyServlet] Proxy servlet is 
disabled
2021-06-04 09:35:13,828 INFO  
[io.hawt.web.servlets.JolokiaConfiguredAgentServlet] Jolokia overridden 
property: [key=policyLocation, 
value=file:/dados/activeMQ/my-cluster/etc/jolokia-access.xml]
2021-06-04 09:35:14,102 INFO  [org.apache.activemq.artemis] AMQ241001: HTTP 
Server started at http://0.0.0.0:8161
2021-06-04 09:35:14,103 INFO  [org.apache.activemq.artemis] AMQ241002: Artemis 
Jolokia REST API available at http://0.0.0.0:8161/console/jolokia
2021-06-04 09:35:14,103 INFO  [org.apache.activemq.artemis] AMQ241004: Artemis 
Console available at http://0.0.0.0:8161/console



Am I correct on supposing it is possible to have 2 bakckups for one master?

All tips and tricks will be welcome!


Enviado do Email<https://go.microsoft.com/fwlink/?LinkId=550986> para Windows 10

Reply via email to