Diogo Sousa created CASSANDRA-10204:
---------------------------------------
Summary: If a node of a cluster fails to write to the commit log
it does not propertly handle it leading to a cluster inconsistency
Key: CASSANDRA-10204
URL: https://issues.apache.org/jira/browse/CASSANDRA-10204
Project: Cassandra
Issue Type: Bug
Reporter: Diogo Sousa
Fix For: 2.1.x
In a cluster of a few nodes (not all of them shown below) I notice through
{nodetool status} that different nodes had different views of who is UP/DOWN.
I also notice than after issuing a {drop keyspace foo} to all nodes did that.
When I grep the logs for error I saw that one of the nodes could not write to
the commit log due to some permission problem:
{code}
[cassandra0] INFO 23:15:17 Solr indexing error log is not enabled
[cassandra0] INFO 23:15:17 Initializing Solr document validation error
log plugin...
[cassandra1] INFO 23:15:16 Solr indexing error log is not enabled
[cassandra1] INFO 23:15:16 Initializing Solr document validation error
log plugin...
[cassandra2] INFO 23:15:18 Solr indexing error log is not enabled
[cassandra2] INFO 23:15:18 Initializing Solr document validation error
log plugin...
[cassandra3] INFO 23:15:17 Solr indexing error log is not enabled
[cassandra3] INFO 23:15:17 Initializing Solr document validation error
log plugin...
[cassandra3] ERROR 23:15:21 Failed managing commit log segments. Commit
disk failure policy is stop; terminating thread
[cassandra3] org.apache.cassandra.io.FSWriteError:
java.io.FileNotFoundException:
/u01/commitlog/CommitLog-4-1440544518541.log (Permission denied)
[cassandra4] INFO 23:15:19 Solr indexing error log is not enabled
[cassandra4] INFO 23:15:19 Initializing Solr document validation error
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
