Bug 676670 - Replication configuration according to MRG UG is not up2date
Summary: Replication configuration according to MRG UG is not up2date
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: Messaging_Programming_Reference
Version: 1.3
Hardware: Unspecified
OS: Unspecified
medium
unspecified
Target Milestone: 1.3.3
: ---
Assignee: Alison Young
QA Contact: Petr Matousek
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-02-10 17:05 UTC by Petr Matousek
Modified: 2012-09-21 12:58 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 723749 (view as bug list)
Environment:
Last Closed: 2011-08-12 05:16:53 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Petr Matousek 2011-02-10 17:05:26 UTC
Description of problem:

1.) 9.1.2. Configuring Queue Replication on the Backup Broker
step 1:
No module needs to be loaded
following replication modules are loaded by default:
replication_exchange.so
replicating_listener.so

I suggest to replace this step with the following sentence:
Ensure that the replication exchange plugin is loaded.

Note can be added ie.:
To ensure the replication exchange plugin is configured, verify that the following library is present on the system (depending on architecture)
/usr/lib64/qpid/daemon/replication_exchange.so
/usr/lib/qpid/daemon/replication_exchange.so

The same for: 9.1.1. Configuring Queue Replication on the Source Broker
I suggest to add a new  first point:
Ensure that the replicating listener plugin is loaded.

Note can be added ie.:
To ensure the replicating listener plugin is configured, verify that the following library is present on the system (depending on architecture)
/usr/lib64/qpid/daemon/replicating_listener.so
/usr/lib/qpid/daemon/replicating_listener.so

2.)  9.1.2. Configuring Queue Replication on the Backup Broker
step 4:
$ qpid-config --broker-addr backup-host add queue replicated-queue --generate-queue-events 2

Option "--generate-queue-events 2" makes no sense on destination broker.
Remove the option, so the command looks like:
$ qpid-config --broker-addr backup-host add queue replicated-queue

Version-Release number of selected component (if applicable):
Red Hat Enterprise MRG 1.3 - Messaging User Guide
Revision 2.4

How reproducible:
n/a

Steps to Reproduce:
n/a
  
Actual results:
Configuring replication according to MRG UG is not up2date

Expected results:
Configuring replication according to MRG UG is up2date

Additional info:
n/a

Comment 5 Petr Matousek 2011-07-21 11:17:28 UTC
9.1.1. Configuring Queue Replication on the Source Broker:

The first point of this paragraph was REPLACED with the new text, which is bad.

There shall be ADDED a NEW first point before the original first point in  9.1.1 as suggested in Comment 0, all the other points must remain untouched (inclusive the original point 1).

So the text shall look like example below:

1. Ensure the replicating listener plugin is loaded.
To ensure the replicating listener plugin is configured, verify that the following library is present on the system. Depending on the system architecture the library is /usr/lib64/qpid/daemon/replicating_listener.so or /usr/lib/qpid/daemon/replicating_listener.so 

2. When you start the MRG Messaging broker, specify the name of the replication event queue
using the --replication-queue option. This can be the name of an existing durable queue
created for the purpose, or the --create-replication-queue option can be used to indicate
that a new transient queue should be created with the specified name. Let's add these options to
qpidd.conf, creating a replication event queue named replication-queue when the broker
starts.
replication-queue=replication-queue
create-replication-queue=true

...

Comment 9 Petr Matousek 2011-07-22 08:33:21 UTC
Messaging User Guide was updated accordingly.

Red Hat Enterprise MRG 1.3 - Messaging User Guide
(Revision 3-2)

-> VERIFIED


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