cassandra如何处理文件系统分区

我的情况： 我有一个带有多个硬盘的服务器

如果我在服务器上安装cassandra（2.1.9）并使用所有硬盘。 如果一个硬盘坏了怎么办

它将只黑名单（硬盘）分区，并将分区（cassandra分区）移动到其他节点或同一节点上的系统分区

它将被视为整个节点都崩溃了

---

该行为在cassandra.yaml中使用

磁盘故障\u策略

设置进行配置。见文件

---

您可以找到有关如何从磁盘故障中恢复的文档。Cassandra不会自动将数据从故障磁盘移动到良好磁盘。需要手动干预才能纠正此问题。

请注意，您可以在节点停止时手动移动文件，并在文件位于其他文件夹中后重新启动。

disk_failure_policy: (Default: stop) Sets how Cassandra responds to disk failure.
    Recommend settings are stop or best_effort.

die - Shut down gossip and Thrift and kill the JVM for any file system errors 
    or single SSTable errors, so the node can be replaced.

stop_paranoid - Shut down gossip and Thrift even for single SSTable errors.

stop - Shut down gossip and Thrift, leaving the node effectively dead,
    but available for inspection using JMX.

best_effort - Stop using the failed disk and respond to requests based on 
    the remaining available SSTables. This means you will see obsolete data 
    at consistency level of ONE.

ignore - Ignores fatal errors and lets the requests fail; all file system 
    errors are logged but otherwise ignored. Cassandra acts as in versions
    prior to 1.2.