activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Tim Bain <>
Subject Re: Shared File System Master Slave
Date Mon, 09 Apr 2018 05:05:42 GMT
The documentation you linked to is for the AMQ message store, not the
KahaDB message store. So if you're using KahaDB as you say, then the page
you linked to is irrelevant.

KahaDB behaves as I described. You only risk losing messages that have not
yet been accepted (i.e. you don't risk losing anything). If I recall
correctly, the only thing that's flushed to disk periodically is the index,
and that can be rebuilt from the raw journal files so there's no risk of
data loss, just a slower broker startup.


On Sun, Apr 8, 2018, 10:06 PM norinos <> wrote:

> As you say, I'm using KahaDB.
> > You asked whether subscriptions would be on the new master, and the
> answer
> > depends on whether the subscription was durable. If it was a durable
> > subscription, the subscription information is persisted and the
> > subscription will be in the same state on the new master, even if the
> > client doesn't immediately reconnect. If the subscription is not durable,
> > then it will be recreated when the client reconnects to the new master,
> so
> > any messages that were unconsumed at the time the original master went
> > down
> > and any messages sent before the client reconnects will be lost for that
> > subscriber.
> I'm using durable subscription.
> So, I understand that clients can receive the message without problems
> when switching from master to slave.
> Please tell me a little more.
> ActiveMQ insert cache index into the reference store for performance at
> checkpoint interval.
> If master goes down, it seems that chache index can not insert.
> So reference store is not up-to-date.
> In this case, if I startup up ActiveMQ, Is the reference store updated at
> the start-up phase?
> --
> Sent from:

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message