Follow

Cassandra Commit Log Corruption

Created by: Herman Wong
Created date:
Last Updated date:

Problem

The "Cassandra" service will not start successfully, after a new hash set was imported.

Solution

If it is determined that Cassandra was running successfully until a recent import of hash data, then it could be that the Cassandra commit logs are corrupted.

To remove commit logs and allow Cassandra to recreate them:

1. Delete the commitlog folder located at: C:\Program Files\AccessData\Cassandra\data\
2. Restart the computer.

Overview

See the "apache.org" links below for additional detail.

This webpage describes a commit log corruption issue in cassandra 3.1.1

https://issues.apache.org/jira/browse/CASSANDRA-12607

If commit log repair is set to occur automatically, then see below to allow Cassandra to ignore corruption upon subsequent starts.

http://mail-archives.apache.org/mod_mbox/cassandra-user/201707.mbox/%3CCAOMBhUiVkP=PRBkuwOqgjrzVBfbTNx70w9D=o-UWsqt9kU5BeA@mail.gmail.com%3E

 

  

Applies To

Cassandra (which is the KFF service for Accessdata application versions 6.3 and later)

FTK/AD Enterprise/AD Lab version 6.3 and above

Summation Pro/AD Ediscovery version 6.3 and above

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

Comments

Powered by Zendesk