[QPID-4630] HA Fix starting from persistent store.

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Component/s: C++ Clustering
• Assignee: Alan Conway
• Reporter: Alan Conway
• Created: 06/Mar/13 20:57
• Updated: 06/Sep/16 16:21
• Resolved: 07/Mar/13 17:27

Description

This was implemented as QPID-4325 but was broken by subsequent changes.

When re-starting a persistent HA cluster, the broker that becomes primary should
keep its store data while all the backup brokers should discard their store data
and catch up from the primary. Backups cannot simply use their own stores
because sequence numbers of stored messages will not match on all brokers. The
backup erases individual queues and exchanges as the catch-up process gets to
them.

To reproduce: see tests in qpid/cpp/src/tests/ha_store_tests.py