Winsdom Chen created CASSANDRA-5453:
---------------------------------------
Summary: AssertionError exception in system.log
Key: CASSANDRA-5453
URL: https://issues.apache.org/jira/browse/CASSANDRA-5453
Project: Cassandra
Issue Type: Bug
Components: Core
Affects Versions: 1.1.0
Environment: five nodes in cluster running on Cent O.S 5.4
Reporter: Winsdom Chen
We've lot of error appeared in one node,
ERROR [Thrift:91817] 2013-03-24 03:26:17,528 AbstractCassandraDaemon.java (line
134) Exception in thread Thread[Thrift:91817,5,main]
java.lang.AssertionError
at
org.apache.cassandra.db.SliceFromReadCommand.maybeGenerateRetryCommand(SliceFromReadCommand.java:78)
at
org.apache.cassandra.service.StorageProxy.fetchRows(StorageProxy.java:775)
at org.apache.cassandra.service.StorageProxy.read(StorageProxy.java:605)
at
org.apache.cassandra.thrift.CassandraServer.readColumnFamily(CassandraServer.java:115)
at
org.apache.cassandra.thrift.CassandraServer.getSlice(CassandraServer.java:270)
at
org.apache.cassandra.thrift.CassandraServer.multigetSliceInternal(CassandraServer.java:354)
at
org.apache.cassandra.thrift.CassandraServer.get_slice(CassandraServer.java:314)
at
org.apache.cassandra.thrift.Cassandra$Processor$get_slice.getResult(Cassandra.java:2847)
at
org.apache.cassandra.thrift.Cassandra$Processor$get_slice.getResult(Cassandra.java:2835)
at org.apache.thrift.ProcessFunction.process(ProcessFunction.java:32)
at org.apache.thrift.TBaseProcessor.process(TBaseProcessor.java:34)
at
org.apache.cassandra.thrift.CustomTThreadPoolServer$WorkerProcess.run(CustomTThreadPoolServer.java:186)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:636)
After such error occur, it will crash. Restart cassandra will work temporary,
but a month later, the case still happened. Not sure if it's due to data
corrupted.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
