Its 'text'.  Don't know the answer of the 2nd question.

On Mon, Oct 24, 2016 at 6:31 PM, Jonathan Haddad <jon@jonhaddad.com> wrote:
What type is board id? Is the value a tombstone?

On Mon, Oct 24, 2016 at 1:38 AM Ali Akhtar <ali.rac200@gmail.com> wrote:
Thanks, but I did come across those, it doesn't look like they provide a resolution.

On Mon, Oct 24, 2016 at 1:36 PM, DuyHai Doan <doanduyhai@gmail.com> wrote:

On Mon, Oct 24, 2016 at 10:24 AM, Ali Akhtar <ali.rac200@gmail.com> wrote:
Any workarounds that don't involve me having to figure out how to uninstall and re-install a different version?

On Mon, Oct 24, 2016 at 1:24 PM, Ali Akhtar <ali.rac200@gmail.com> wrote:
3.9..

On Mon, Oct 24, 2016 at 1:22 PM, DuyHai Doan <doanduyhai@gmail.com> wrote:
Which version of C* ? There was similar issues with commitlogs in tic-toc versions.

On Mon, Oct 24, 2016 at 4:18 AM, Ali Akhtar <ali.rac200@gmail.com> wrote:
I have a single node cassandra installation on my dev laptop, which is used just for dev / testing.

Recently, whenever I restart my laptop, Cassandra fails to start when I run it via 'sudo service cassandra start'.

Doing a tail on /var/log/cassandra/system.log gives this log:

INFO  [main] 2016-10-24 07:08:02,950 CommitLog.java:166 - Replaying /var/lib/cassandra/commitlog/CommitLog-6-1476907676969.log, /var/lib/cassandra/commitlog/CommitLog-6-1476907676970.log, /var/lib/cassandra/commitlog/CommitLog-6-1477269052845.log
ERROR [main] 2016-10-24 07:08:03,357 JVMStabilityInspector.java:82 - Exiting due to error while processing commit log during initialization.
org.apache.cassandra.db.commitlog.CommitLogReadHandler$CommitLogReadException: Unexpected error deserializing mutation; saved to /tmp/mutation9186356142128811141dat.  This may be caused by replaying a mutation against a table with the same name but incompatible schema.  Exception follows: org.apache.cassandra.serializers.MarshalException: Not enough bytes to read 0th field board_id
at org.apache.cassandra.db.commitlog.CommitLogReader.readMutation(CommitLogReader.java:410) [apache-cassandra-3.9.jar:3.9]
at org.apache.cassandra.db.commitlog.CommitLogReader.readSection(CommitLogReader.java:343) [apache-cassandra-3.9.jar:3.9]
at org.apache.cassandra.db.commitlog.CommitLogReader.readCommitLogSegment(CommitLogReader.java:202) [apache-cassandra-3.9.jar:3.9]
at org.apache.cassandra.db.commitlog.CommitLogReader.readAllFiles(CommitLogReader.java:85) [apache-cassandra-3.9.jar:3.9]
at org.apache.cassandra.db.commitlog.CommitLogReplayer.replayFiles(CommitLogReplayer.java:135) [apache-cassandra-3.9.jar:3.9]
at org.apache.cassandra.db.commitlog.CommitLog.recoverFiles(CommitLog.java:187) [apache-cassandra-3.9.jar:3.9]
at org.apache.cassandra.db.commitlog.CommitLog.recoverSegmentsOnDisk(CommitLog.java:167) [apache-cassandra-3.9.jar:3.9]
at org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:323) [apache-cassandra-3.9.jar:3.9]
at org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:601) [apache-cassandra-3.9.jar:3.9]
at org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:730) [apache-cassandra-3.9.jar:3.9]


I then have to do 'sudo rm -rf /var/lib/cassandra/commitlog/*' which fixes the problem, but then I lose all of my data.

It looks like its saying there wasn't enough data to read the field 'board_id', any ideas why that would be?