Skip to content
This repository has been archived by the owner on Feb 27, 2020. It is now read-only.

Commit

Permalink
Merge pull request #124 from Metaswitch/multi-mark-node-failed
Browse files Browse the repository at this point in the history
Reviewer [EM] - Mark node failed, multiple nodes
  • Loading branch information
johadalin committed Nov 9, 2015
2 parents 9306841 + b74fe67 commit 98f1022
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion docs/Handling_Failed_Nodes.md
Original file line number Diff line number Diff line change
Expand Up @@ -48,7 +48,7 @@ To recover from this state:

## Removing a Node From a Data Store

The `mark_node_failed` script can be used to remove a failed node from a back-end data store. You will need to know the type of the failed node (e.g. "sprout") and its IP address. To remove the failed node log onto a working node in the same site and run the following commands (depending on the failed node's type).
The `mark_node_failed` script can be used to remove a failed node from a back-end data store. You will need to know the type of the failed node (e.g. "sprout") and its IP address. To remove the failed node log onto a working node in the same site and run the following commands (depending on the failed node's type). If you are removing multiple nodes simultaneously, ensure that you run the `mark_node_failed` scripts for each store type simultaneously (e.g. for multiple sprout removal, mark all failed nodes for memcached simultaneously first, and then mark all failed nodes for chronos).

If you cannot log into a working node in the same site (e.g. because an entire geographically
redundant site has been lost), you can use a working node in the other site, but in this case you
Expand Down

0 comments on commit 98f1022

Please sign in to comment.