In that scenario if your master's disk fails your messages are toast. It also assumes the master comes back online while the messages are still relevant. It's not a HA config. On Oct 28, 2010, at 10:45 AM, kseelam wrote:
> > Hi, > > We have tested with 2 brokers as Master/slave, if any messages are not yet > persisted (but they are in the Journal) while switching form master to > slave; those messages are persisting fine when that broker become the Master > again. Only downside is, those massages have to wait till that broker become > the Master to be persisted. We did not find any messages loosing. Any other > downsides of this approach? > > Thanks lot > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/JDBC-Master-Slave-approach-with-Journal-for-HA-tp3014521p3017374.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com.
