The procedure for recovering a failed Storage Node failure depends upon the type of failure, and the type of Storage Node that has failed.
Use this table to help decide how to respond to a Storage Node failure. Links to the complete procedures follow the table.
| Issue | Action | Notes |
|---|---|---|
| More than one Storage Node has failed? | Contact technical support. | Under some circumstances, recovering more than one Storage Node might affect the integrity of the Cassandra database. Technical support can determine when it is safe to begin recovery of a second Storage Node. |
A second Storage Node fails less than 15 days after a Storage Node failure or recovery?
|
Contact technical support. | |
| Storage Node has been offline for more than 15 days? | Recover a Storage Node down > 15 days | This procedure is required to ensure Cassandra database integrity. |
| Appliance Storage Node has failed? | Recover an appliance Storage Node Major steps:
|
The recovery procedure for appliance Storage Nodes is the same for all failures. |
| Storage volumes have failed? (system drive is intact) |
Recover from storage volume failure Major steps:
|
This procedure is used for virtual Storage Nodes. |
| System drive and possibly storage volumes have failed? | Recover from system drive failure Major steps:
|
The node replacement procedure varies depending on the deployment platform. Linux: For Linux deployments, Storage Node recovery steps after node replacement might be different than shown here. See Linux node replacement for details.
|