Thanks for the reply. We've tested both settings and we have the following
concerns. We would like to have a HA setting using master/slave and we want
to find out how to setup HA mysql database correctly. Please advise.
1) For Federated network of brokers, only one broker will persist messages
Am 19.07.2013 00:49, schrieb slam:
Hi Christian,
In your multi master MySql setup, did you replicate the data? If not, will
you lose messages if one of the MySql servers that contains messages
failed/shut down?
assuming you did refer to me.
I do not run MySQL replication, like Master-Master
You can do federated network of brokers, but in that case you rely on
brokers to share messages between each other in a store-and-forward manner.
With a master/slave set up where you have a broker elected master, and a
slave sitting standby, they end up sharing a mysql database, thus when the
maste
Hi Christian,
In your multi master MySql setup, did you replicate the data? If not, will
you lose messages if one of the MySql servers that contains messages
failed/shut down?
--
View this message in context:
http://activemq.2283324.n4.nabble.com/ActiveMQ-Master-slave-with-MySQLCluster-ba
Hi;
I have master/slave MQ setup with Multi master mesh Mysql back end. With the
following configurations, the failover works perfectly. Take down any DB
host that MQ is connected to, it connects to the next available DB host
automatically. No need to restart. Hope it helps:
That seems very reasonable.
The locker implementation can specified via configuration, it would be
great if you could provide an implementation that you can verify with
your setup.
note the interface:
http://svn.apache.org/viewvc/activemq/trunk/activemq-core/src/main/java/org/apache/activemq/store/
Am 01.02.2012 17:57, schrieb Christian Hilgers:
Any Updates/comments here?
Am 31.01.2012 14:13, schrieb Gary Tully:
This need some work.
On 5.6, a single broker can deal with a failover of the jdbc store.
The difficulty is locking in the master/slave case, or peer cluster case.
The current lo
Am 31.01.2012 14:13, schrieb Gary Tully:
This need some work.
On 5.6, a single broker can deal with a failover of the jdbc store.
The difficulty is locking in the master/slave case, or peer cluster case.
The current lock impl (who's job it is to get an exclusive lock on the
store) treats failure
This need some work.
On 5.6, a single broker can deal with a failover of the jdbc store.
The difficulty is locking in the master/slave case, or peer cluster case.
The current lock impl (who's job it is to get an exclusive lock on the
store) treats failure of a lock as a fatal event and stops the b
