cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Romain Hardouin <>
Subject Re: unrecognized column family in logs
Date Fri, 10 Nov 2017 07:39:27 GMT
 Does "nodetool describecluster" shows an actual schema disagreement?You can try "nodetool
resetlocalschema" to fix the issue on the node experiencing disagreement.
    Le jeudi 9 novembre 2017 à 02:55:22 UTC+1, Erick Ramirez <>
a écrit :  
 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
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 <> wrote:



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 - Attempted
to write commit log entry for unrecognized column family: 2854d160-3a2f-11e6-925c- b143135bdc80 cassandra/blob/master/src/ java/org/apache/cassandra/db/ commitlog/CommitLogSegment.


The column family has heavy writes, but it hasn’t changed schema / load wise recently. How
can this be troubleshooted / fixed ?


Thanks !




View raw message