[ 
https://issues.apache.org/jira/browse/QPID-5421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13847817#comment-13847817
 ] 

ASF subversion and git services commented on QPID-5421:
-------------------------------------------------------

Commit 1550819 from [~aconway] in branch 'qpid/trunk'
[ https://svn.apache.org/r1550819 ]

QPID-5421: HA replication error in stand-alone replication

There were replication errors because with stand-alone replication an IdSetter
was not set on the original queue until queue replication was set up. Any
messages on the queue *before* replication was setup had 0 replication IDs. When
one of those messages was dequeued on the source queue, an incorrect message was
dequeued on the replica queue.

The fix is to add an IdSetter to every queue when replication is enabled.

The unit test  ha_tests.ReplicationTests.test_standalone_queue_replica has been
updated to test for this issue.

This commit also has some general tidy-up work around IdSetter and 
QueueSnapshot.

> HA replication error in stand-alone replication.
> ------------------------------------------------
>
>                 Key: QPID-5421
>                 URL: https://issues.apache.org/jira/browse/QPID-5421
>             Project: Qpid
>          Issue Type: Bug
>          Components: C++ Clustering
>    Affects Versions: 0.24
>            Reporter: Alan Conway
>            Assignee: Alan Conway
>
> When using standalone replication between two brokers, there will be 
> replication errors if messages are put onto the primary queue before 
> replication is set up.
> To reproduce:
> Create queue "q" on brokers P and B.
> Put messages 1,2,3 on P.q
> Start replication from P.q to B.q
> Put messages 4,5,6 o P.q
> Fetch and acknowledged one message from P.q
> Fetch all messages from B.q. Instead of the expected messages [1,2,3,4,5], q 
> has [0,1,3,4,5]



--
This message was sent by Atlassian JIRA
(v6.1.4#6159)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to