Sample Error Message:

ERROR main 2019-09-18 09:47:39,700 LogFile.java:161 - Failed to read records for transaction log [mc_txn_anticompactionafterrepair_4e3c04d0-da17-11e9-94b2-8f6a02d908a5.log in /data1/cassandra/OpsCenter/settings-a1cac25045bf11e8a7085d2e0fe1c518, /data2/cassandra/OpsCenter/settings-a1cac25045bf11e8a7085d2e0fe1c518]

What does this ERROR message mean?

This error will be logged when DSE/Cassandra cannot process a transaction log. This is a top-level log entry, there will be additional log entries noting the specific reason for the "Failed to read records for transaction log" message.

Transaction log files track SSTable activity such as compaction, flushing, and streaming. On startup, transaction logs are used to clean-up any partial transactions that were in progress when the DSE/Cassandra process exited. To avoid file system errors, such as disk corruption, a failed read on a transaction log will always prevent the node to start.

Why does this error occur?

• Duplicate Records: Please see link to Support 1117 article for more information.
• Disk failure due to Transaction Log Bug: Please see Unexpected disk state: failed to read transaction log(https://support.datastax.com/hc/en-us/articles/360013621497-ERROR-Unexpected-disk-state-failed-to-read-transaction-log)
• DSE/Cassandra crash or JBOD Disk Failure: Please see link to Support 1118 article for more information.

How do you fix this ERROR?

• Duplicate Records: Please see link to Support 1117 article for more information.
• Disk failure due to Transaction Log Bug: Please see Unexpected disk state: failed to read transaction log(https://support.datastax.com/hc/en-us/articles/360013621497-ERROR-Unexpected-disk-state-failed-to-read-transaction-log)
• DSE/Cassandra crash or JBOD Disk Failure: Please see link to Support 1118 article for more information.