diff options
| author | Alan Conway <aconway@apache.org> | 2012-06-21 16:05:09 +0000 |
|---|---|---|
| committer | Alan Conway <aconway@apache.org> | 2012-06-21 16:05:09 +0000 |
| commit | 30133c25a10861ca9e589e22c13bea4dd99f4c0f (patch) | |
| tree | aa8ff676fd4467b92c8138e68d6a8a5da1cb535a /java/test-profiles/python_tests/Java010PythonExcludes | |
| parent | f3900f98ccddc80daf4ad18e4acf718504864b7a (diff) | |
| download | qpid-python-30133c25a10861ca9e589e22c13bea4dd99f4c0f.tar.gz | |
QPID-4082: cluster de-sync after broker restart & queue replication
Having queue state replication between 2 clusters, restarting a broker in both
source+destination clusters sometimes leads to cluster de-sync. No QMF
communication is involved, though symptoms are similar to the bug caused by
missing propagation of QMF errors within a cluster.
The bug is caused by "deliveryCount" in SemanticState::ConsumerImpl
(qpid/broker/SemanticState.cpp) not being replicated to a joining cluster node
during catch-up. When the elder broker in src.cluster sends session.sync() after
sending 5 messages (per --ack 5 in qpid-route), the recently joiner node in
src.cluster does not do so, what leads to the cluster de-sync.
The patch:
- adds to "consumer-state" method (see xml/cluster.xml file change) to update a new joi-ner a new property deliveryCount
- updates cluster::Connection::consumerState to send deliveryCount to the method
- updates cluster::Connection::consumerState to set the received deliveryCount
- add two methods to broker::SemanticState::ConsumerImpl for getting and setting deliveryCount
git-svn-id: https://svn.apache.org/repos/asf/qpid/trunk/qpid@1352588 13f79535-47bb-0310-9956-ffa450edef68
Diffstat (limited to 'java/test-profiles/python_tests/Java010PythonExcludes')
0 files changed, 0 insertions, 0 deletions