Bug 579805

Summary: New tool for setting status of cluster store.
Product: Red Hat Enterprise MRG Reporter: Alan Conway <aconway>
Component: Messaging_Programming_ReferenceAssignee: Jonathan Robie <jonathan.robie>
Status: CLOSED DUPLICATE QA Contact: MRG Quality Engineering <mrgqe-bugs>
Severity: medium Docs Contact:
Priority: medium    
Version: 1.0CC: gsim
Target Milestone: 1.3   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-06-01 19:32:33 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Alan Conway 2010-04-06 15:37:17 UTC 
Description of problem:

Need to add a short section on persistent clusters along the lines of this:

In the unlikely event that every member of persistent cluster crashes and none of them have a clean store (e.g. if a power failure shut down all members simultaneously) you can recover as follows:

1. Choose one member and force its store to a clean state as follows: 
 
  qpid-cluster-store --mark-clean <path to broker's data directory>

If the brokers all fail so close together that there is no clean store, then there's no easy way to determine which store is the "best".

2. Start the member with the clean store first, wait for it to log a "ready" message.

3. Then start the remaining members, they will download state from the first member.
Comment 1 Alan Conway 2010-06-01 19:32:33 UTC 

*** This bug has been marked as a duplicate of bug 598653 ***