one.
(the first backupnode can be gone because it crashed or was stopped; or because
it became the new master due to a failing original master)
e.
-Oorspronkelijk bericht-
Van: Edson Richter
Verzonden: vrijdag 4 juni 2021 14:58
Aan: users@activemq.apache.org
Onderwerp: Master+slave+sl
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:
tcp://sc0b03:61616
tcp://pr0b03:61616
tcp://sp0b03:61616
xx
?
Thank you.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Pure-Master-Slave-Slave-keeps-the-messages-already-deleted-from-Master-tp4263867p4263867.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
You may need to look at share file system or JDBC master slave
configuration.
The group clustering type replication with automatic group additions is
something that will be addressed in the 6.0 time frame. Some initial support
for replicating persistent messages is already part of KahaDB, it may b
pure master slave is handy for data replication but is lock step rather than
catch up, is limited to a single pair and has no auto recovery strategy.
Master slave with a shared file system or shared database is what you want
for fault tolerance. The first to obtain a lock is a master and the next
We also plan to use master/slave.
The 'waitForSlave' seems a bit strange for me, since our main reason for
adding some slaves is to avoid a single point of failure (i.e. the
master). But what if the slave fails? Does the required 'waitForSlave'
mean that we can't run a master without his slave
Thank you for your reply.
I know about the 'waitForSlave' attribute, but it is not really what I need.
I would like to be able to add a backup machine (and hence a slave broker)
at some later time, without having to restart the master broker and all the
producer/consumer connections to it. I would
the brokers need to be in sync from the start. there is a waitForSlave
attribute that can force the master to stall till the slave connects. see:
https://issues.apache.org/activemq/browse/AMQ-596
2009/7/29 brendanr
>
> Hi,
>
> I am having an issue with a simple master/slave setup. My master is r
Hi,
I am having an issue with a simple master/slave setup. My master is running
on one machine (192.168.10.141), and my slave is running on a separate
machine (192.168.10.1). Attached are the config files for both master and
slave, and the log files for master and slave. I am running broker versi
Hello;
We are using activemq 4.1.1 with failover capability. The two brokers run on
a separate machine as master/slave and they share the same data source which
is oracle 10g for message persistence. So everything was working as expected
until I got a call from the DBA that the salve broker is ca
Hi,
I am using Jboss 4.0.4, oracle, and activemq 4.1.1 JDBC master/salve.
I am using activemq-rar-4.1.1.rar under my deploy/ folder.
broker configuration is as:
My problem is : After master server launched successfully. My slave server
is halt when try to Attempting to acquire the exc
11 matches
Mail list logo
