Bug 489004 - Newly joined node may end up with duplicate enqueue events on replication queue
Summary: Newly joined node may end up with duplicate enqueue events on replication queue
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: qpid-cpp
Version: Development
Hardware: All
OS: Linux
high
high
Target Milestone: 1.1.1
: ---
Assignee: Gordon Sim
QA Contact: Frantisek Reznicek
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-03-06 17:31 UTC by Gordon Sim
Modified: 2015-11-16 00:07 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-06-28 18:50:17 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Gordon Sim 2009-03-06 17:31:59 UTC
State for replication queue will be transfered to the newly joining node therefore event generation should be suppressed when enqueing messages on other queues as part of the catchup.

Comment 1 Gordon Sim 2009-03-09 16:02:08 UTC
Fixed by r751719.

Test procedure (e.g.):

(1) start primary cluster node (node_1), 
(2) declare queue with --generate-queue-events 2, 
(3) send messages to this node,
(4) consume half of those messages (again through connecting to this node) 
(5) now add second node to that cluster (node_2), 
(6) start a dr broker and establish a bridge from node_2 to that broker, 
(7) check that replication to dr broker works and that only expected messages are on the replicated queue

There is a test checked into qpid svn (clustered_replication_test) that may be useful and is run during make check.

Comment 2 Martin Kudlej 2009-04-17 12:49:15 UTC
Tested on r750054 and it didn't work as I expected.
Testend on r752581 and it works. clustered_replication_test passed.
-->VERIFIED


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