It looks like you have a schema disagreement in your cluster which you need to look into.
And you're right since that column family ID is equivalent to Friday, June 24, 2016 10:14:49 AM PDT. Have a look at the table IDs in system.schema_columnfamilies for clues. Cheers! On Thu, Nov 9, 2017 at 4:50 AM, Anubhav Kale < anubhav.k...@microsoft.com.invalid> wrote: > Hello, > > > > We run Cassandra 2.1.13 and since last few days we’re seeing below in logs > occasionally. The node then becomes unresponsive to cqlsh. > > > > ERROR [SharedPool-Worker-2] 2017-11-08 17:02:32,362 > CommitLogSegment.java:441 - Attempted to write commit log entry for > unrecognized column family: 2854d160-3a2f-11e6-925c-b143135bdc80 > > > > https://github.com/mariusae/cassandra/blob/master/src/ > java/org/apache/cassandra/db/commitlog/CommitLogSegment.java#L95 > > > > The column family has heavy writes, but it hasn’t changed schema / load > wise recently. How can this be troubleshooted / fixed ? > > > > Thanks ! > > > > > > >