Re: unrecognized column family in logs

2017-11-12 Thread Erick Ramirez
nodetool describecluster will show (a) if there are multiple schema versions, and/or (b) unreachable nodes. Cheers! On Fri, Nov 10, 2017 at 6:39 PM, Romain Hardouin < romainh...@yahoo.fr.invalid> wrote: > Does "nodetool describecluster" shows an actual schema disagreement? > You can try "nodetool

Re: unrecognized column family in logs

2017-11-09 Thread Romain Hardouin
Does "nodetool describecluster" shows an actual schema disagreement?You can try "nodetool resetlocalschema" to fix the issue on the node experiencing disagreement. Romain Le jeudi 9 novembre 2017 à 02:55:22 UTC+1, Erick Ramirez a écrit : It looks like you have a schema disagreement in

Re: unrecognized column family in logs

2017-11-08 Thread Erick Ramirez
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:

unrecognized column family in logs

2017-11-08 Thread Anubhav Kale
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: 2854d