[ 
https://issues.apache.org/jira/browse/CASSANDRA-11934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Joel Knighton resolved CASSANDRA-11934.
---------------------------------------
       Resolution: Duplicate
    Reproduced In:   (was: 3.5)

> System keyspace corruption 
> ---------------------------
>
>                 Key: CASSANDRA-11934
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-11934
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>         Environment: Have seen on Mac and CoreOS
>            Reporter: Robert Marshall
>
> A node that fails to gossip with seeds on initial startup appears to cause a 
> corruption of the system keyspace.
> To reproduce sets seed to invalid address and start node.
> It will fall over with:
> Exception (java.lang.RuntimeException) encountered during startup: Unable to 
> gossip with any seeds
> java.lang.RuntimeException: Unable to gossip with any seeds
> Then upon restarting cassandra a configuration exception will be seen, 
> indicating a problem with the system keyspace
> ERROR 06:01:26 Fatal exception during initialization
> org.apache.cassandra.exceptions.ConfigurationException: Found system keyspace 
> files, but they couldn't be loaded!
>       at 
> org.apache.cassandra.db.SystemKeyspace.checkHealth(SystemKeyspace.java:907) 
> ~[apache-cassandra-3.5.jar:3.5]
>       at 
> org.apache.cassandra.service.StartupChecks$8.execute(StartupChecks.java:304) 
> ~[apache-cassandra-3.5.jar:3.5]
>       at 
> org.apache.cassandra.service.StartupChecks.verify(StartupChecks.java:107) 
> ~[apache-cassandra-3.5.jar:3.5]
>       at 
> org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:169) 
> [apache-cassandra-3.5.jar:3.5]
>       at 
> org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:551)
>  [apache-cassandra-3.5.jar:3.5]
>       at 
> org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:680) 
> [apache-cassandra-3.5.jar:3.5]



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to