You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@activemq.apache.org by Jason Dixon <jd...@omniti.com> on 2008/02/27 21:09:42 UTC

Synchronization of MasterSlave

We're testing ActiveMQ 5.1 with some php/stomp clients and java  
consumers.  We noticed that messages consumed and deleted off the  
Master broker aren't purged off the Slave broker.  When I first read  
the MasterSlave documentation, I read the following passage and  
assumed it to be referring only to the manual recovery process, given  
the context.  But after seeing this behavior, I can't help but wonder  
if MasterSlave is "broken" in that it doesn't truly synchronize the  
Slave broker while the Master is still active.

"There is no automatic synchronization between brokers. This is a  
manual process."

Can someone clarify this behavior?  Is there a way to enforce that  
deletions are on the Master broker are removed from the Slave as well?

Thanks,

---
Jason Dixon
OmniTI Computer Consulting, Inc.
jdixon@omniti.com
443.325.1357 x.241








Re: Synchronization of MasterSlave

Posted by Rob Davies <ra...@gmail.com>.
On 27 Feb 2008, at 20:09, Jason Dixon wrote:

> We're testing ActiveMQ 5.1 with some php/stomp clients and java  
> consumers.  We noticed that messages consumed and deleted off the  
> Master broker aren't purged off the Slave broker.  When I first read  
> the MasterSlave documentation, I read the following passage and  
> assumed it to be referring only to the manual recovery process,  
> given the context.  But after seeing this behavior, I can't help but  
> wonder if MasterSlave is "broken" in that it doesn't truly  
> synchronize the Slave broker while the Master is still active.
>
> "There is no automatic synchronization between brokers. This is a  
> manual process."
>
> Can someone clarify this behavior?  Is there a way to enforce that  
> deletions are on the Master broker are removed from the Slave as well?
>
> Thanks,
>
> ---
> Jason Dixon
> OmniTI Computer Consulting, Inc.
> jdixon@omniti.com
> 443.325.1357 x.241
>
The slave should be keeping in sync with the master's state. The only  
manual synchronization you are required to do is with the message  
stores currently

cheers,

Rob