Thank you for your response!

Just out of curiosity, what is this masterslave:() transport is about then?

Also,  if I don't configure network connection will 
updateClusterClientsOnRemove parameter take effect?

My main concern is that clients will go into stuck state during/after the 
failover. I'm not sure if everything I need is just handle this in the code 
with  TransportListener or do I need to set updateClusterClientsOnRemove and 
updateClusterClients on the broker side to make failover smooth?

-- 
    Vilius

-----Original Message-----
From: Jean-Baptiste Onofre <j...@nanthrax.net> 
Sent: Tuesday, November 30, 2021 7:01 AM
To: users@activemq.apache.org
Subject: Re: ActiveMQ 5.16.x Master/Slave topology question

Hi

No need to use networkConnector with master/slave.

Just use failover on the client side.

So basically,

1. Brokers side, you shared the same filesystem (using NFS, LUN, whatever), and 
you configure kahadb to point on the same filesystem in activemq.xml 2. On 
client side, you can failover:(master,slave) on the brokerURL to allow client 
to automatically switch to “new” master

Regards
JB

> Le 29 nov. 2021 à 21:54, Vilius Šumskas <v.sums...@advantes.tech.INVALID> a 
> écrit :
> 
> Hi,
> 
> I‘m trying to setup a simple ActiveMQ 5.16.x master/slave cluster using 
> shared filesystem option. I just need one broker running at any given time 
> and a slave for HA.
> 
> The filesystem part is clear and I have already configured it according to 
> ActiveMQ requirements.
> 
> What I don’t understand is do I _need_ to configure networkConnectors in 
> order for master/slave to work properly? Almost every configuration example I 
> found on the internet says that in order to have master/slave topology one 
> only needs to point kahaDB to the same shared data directory. Every article 
> and blog post which talk about networkConnectors say that it is only related 
> to Network of Brokers functionality. However this link 
> https://activemq.apache.org/networks-of-brokers#masterslave-discovery says 
> something vague regarding masterslave:// transport. Also there is this blog 
> post 
> https://medium.com/@chamilad/creating-a-simple-activemq-master-slave-setup-e3de33a6bcc2
>  which says that networkConnector is needed?
> 
> Can somebody clear things up? Is master/slave cluster is also considered as 
> network of (two) brokers? Can I run it with or without neworkConnectors, and 
> what is the difference from the perspective of clients then?
> 
> --
>   Best Regards,
> 
>    Vilius
> 

Reply via email to