Delete the file: C:\Program
Files\DataStax-DDC\data\commitlog\CommitLog-6-1542650688953.log and restart
Cassandra. Its possible that you lose a bit of data that just existed on this
log (not matter if you have replica or could re-insert data again) Sent using
Zoho Mail ============ Forwarded message ============ From : Will Mackle
<whalesfromsp...@gmail.com> To : <user@cassandra.apache.org> Date : Sat, 08 Dec
2018 11:56:00 +0330 Subject : Cassandra does launch since computer was
accidentally unplugged ============ Forwarded message ============ Hello, I am
a novice cassandra user and am looking for some insight with respect to my
circumstance: The computer I was using to run cassandra was accidentally
unplugged by my friend, since this event, I have not been able to successfully
relaunch cassandra. I have included a chunk from the log file below. It
looks to me like the corrupt log files are the issue, but I would like to
confirm that that error is not dependent on the earlier JMX error. Does this
JMX error impact cassandra's launch if cassandra is only being accessed by the
computer that cassandra is running on? I have the port assinged in
cassandra-env.sh, so it is really confusing to me why this error occurs. With
respect to the log file corruption, does there exist the capacity to
recover/repair the issue? I'm assuming that if I delete the log file to launch
cassandra that I will lose data.. am I correct in this assumption? I left some
lines out of the log file that were not errors or warnings, if it is important
for me to include them, I can do so, I'm simply not sure if any info from the
log file is a security risk for me to share. INFO 14:50:01 JVM Arguments:
[-ea, -javaagent:C:\Program
Files\DataStax-DDC\apache-cassandra\lib\jamm-0.3.0.jar, -Xms1G, -Xmx1G,
-XX:+HeapDumpOnOutOfMemoryError, -XX:+UseParNewGC, -XX:+UseConcMarkSweepGC,
-XX:+CMSParallelRemarkEnabled, -XX:SurvivorRatio=8, -XX:MaxTenuringThreshold=1,
-XX:CMSInitiatingOccupancyFraction=75, -XX:+UseCMSInitiatingOccupancyOnly,
-Dcom.sun.management.jmxremote.port=7199,
-Dcom.sun.management.jmxremote.ssl=false,
-Dcom.sun.management.jmxremote.authenticate=false,
-Dlog4j.configuration=log4j-server.properties,
-Dlog4j.defaultInitOverride=true, -DCassandra] WARN 14:50:01 JNA link failure,
one or more native method will be unavailable. WARN 14:50:01 JMX is not
enabled to receive remote connections. Please see cassandra-env.sh for more
info. ERROR 14:50:01 cassandra.jmx.local.port missing from cassandra-env.sh,
unable to start local JMX service. WARN 14:50:01 Use of
com.sun.management.jmxremote.port at startup is deprecated. Please use
cassandra.jmx.remote.port instead. --- INFO 14:50:05 Not submitting build
tasks for views in keyspace system as storage service is not initialized WARN
14:50:05 JMX settings in cassandra-env.sh have been bypassed as the JMX
connector server is already initialized. Please refer to cassandra-env.(sh|ps1)
for JMX configuration info INFO 14:50:07 Populating token metadata from system
tables --- INFO 14:50:08 Completed loading (15 ms; 26 keys) KeyCache cache
INFO 14:50:08 Replaying C:\Program
Files\DataStax-DDC\data\commitlog\CommitLog-6-1542650688952.log, C:\Program
Files\DataStax-DDC\data\commitlog\CommitLog-6-1542650688953.log, C:\Program
Files\DataStax-DDC\data\commitlog\CommitLog-6-1542987010987.log, C:\Program
Files\DataStax-DDC\data\commitlog\CommitLog-6-1542987613467.log, C:\Program
Files\DataStax-DDC\data\commitlog\CommitLog-6-1542990216101.log ERROR 14:50:09
Exiting due to error while processing commit log during initialization.
org.apache.cassandra.db.commitlog.CommitLogReadHandler$CommitLogReadException:
Could not read commit log descriptor in file C:\Program
Files\DataStax-DDC\data\commitlog\CommitLog-6-1542650688953.log at
org.apache.cassandra.db.commitlog.CommitLogReader.readCommitLogSegment(CommitLogReader.java:155)
[apache-cassandra-3.9.0.jar:3.9.0] at
org.apache.cassandra.db.commitlog.CommitLogReader.readAllFiles(CommitLogReader.java:85)
[apache-cassandra-3.9.0.jar:3.9.0] at
org.apache.cassandra.db.commitlog.CommitLogReplayer.replayFiles(CommitLogReplayer.java:135)
[apache-cassandra-3.9.0.jar:3.9.0] at
org.apache.cassandra.db.commitlog.CommitLog.recoverFiles(CommitLog.java:187)
[apache-cassandra-3.9.0.jar:3.9.0] at
org.apache.cassandra.db.commitlog.CommitLog.recoverSegmentsOnDisk(CommitLog.java:167)
[apache-cassandra-3.9.0.jar:3.9.0] at
org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:323)
[apache-cassandra-3.9.0.jar:3.9.0] at
org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:601)
[apache-cassandra-3.9.0.jar:3.9.0] at
org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:730)
[apache-cassandra-3.9.0.jar:3.9.0] Any help/insight is much appreciated, Thanks
