Bug 505634 - Feature: allow async replication of queue state to be stopped (and ideally restarted) on live broker
Summary: Feature: allow async replication of queue state to be stopped (and ideally re...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: qpid-cpp
Version: 1.1.1
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
: ---
Assignee: Alan Conway
QA Contact: MRG Quality Engineering
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-06-12 16:55 UTC by Gordon Sim
Modified: 2015-03-01 13:22 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-03-01 13:22:58 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Gordon Sim 2009-06-12 16:55:54 UTC
At present once a queue has been configured to generate events and the replicating event listener plugin has beenactivated there is no way to stop replication in a way that would allow it to be subsequently reactivated without stoppingthe broker instance.

Comment 1 Carl Trieloff 2009-06-30 14:24:20 UTC
Replication can be disabled by using an exchange configuration:

One simple option is to specify a --replication-exchange rather than a --replication-queue on the primary and then bind in a 'normal' queue (recommendation would be to use a fanout exchange).

To 'turn off' replication, you would then simply unbind the queue. Note however you would miss any further events. 


Note that a local broker or client can also be used to drain the queue for off-line recovery.

Comment 2 Justin Ross 2013-02-26 20:42:52 UTC
Alan, does the new ha-based replication currently allow this?

Comment 3 Alan Conway 2013-02-27 19:31:32 UTC
Not yet but it would be simple to add.

Comment 5 Alan Conway 2015-03-01 13:22:58 UTC
The latest release has a new queue replication mechanism based on the new HA module, the old asnync replication is gone. Please open a new BZ if there are any issues/missing features with the new mechanism.


Note You need to log in before you can comment on or make changes to this bug.