Cassandra Start Failure--cassandra Summary (iv)

Recently the inexplicable Cassandra can't be started, and after checking the log in log, I finally found the reason. (The logon log is located in the CASSANDRA folder of the $cassandra_home sibling directory)

Look at the error report first.

ERROR [Sstablebatchopen:2-one-all::  933 Fileutils.java:447"stop"0 chunks Encountered: [Email protected]

Sstable Open failed, because sstable damaged, look at the foreigner's saying

Have some replication would surely help you to fix this without data loss but it would come with a price. Despite all your effort-cannot manage to recover your corrupted sstable. Decide to remove the it from your the file system to start Cassandra again. Replication your data is lost. If you had replication on the cluster, you can possibly fetch the data from other nodes. That's what Nodetool repair does! So Nodetool repair does not repair corrupted sstable. Basicallynodetool repair Compare tables from node to node to find missing or inconsistent data and then repair it. You can find more information on what it works here. However Nodetool repair is very expensive, it's long and uses a lot of CPUs, disk and network. There is the good post about repair benefits and drawbacks.

Encounter sstable Damage This problem solution is to delete the data and then restart the Cassandra, because I use a single node so the data naturally no backup, very pit said, but fortunately only tens of thousands of analysis data, and then inserted into the good. If it is a cluster, you can use Nodetool repair from other nodes to take back the backup data, but the cost is very large, it will take a lot of time, consuming a lot of CPU. So it's better to do a backup.

After deleting the data reboot, it is easy to start successfully. The last line of the startup success log file is:

INFO  [Thread-2] 2015-11-27 16:30:52,550 thriftserver.java:136-listening for thrift clients ...

　　

Cassandra Start Failure--cassandra Summary (iv)