Bug 579805 - New tool for setting status of cluster store.
Summary: New tool for setting status of cluster store.
Keywords:
Status: CLOSED DUPLICATE of bug 598653
Alias: None
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: Messaging_Programming_Reference
Version: 1.0
Hardware: All
OS: Linux
medium
medium
Target Milestone: 1.3
: ---
Assignee: Jonathan Robie
QA Contact: MRG Quality Engineering
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-04-06 15:37 UTC by Alan Conway
Modified: 2013-08-06 00:53 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-06-01 19:32:33 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

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 ***


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