Sounds like you upgraded to trunk from 0.6 without draining your commitlog first?
On Mon, Aug 9, 2010 at 3:30 PM, Arya Goudarzi <agouda...@gaiaonline.com> wrote: > Just throwing this out there as it could be a concern. I had a cluster of 3 > nodes running. Over the weekend I updated to trunc (Aug 9th @ 2pm). Today, I > came to run my daily tests and my client kept giving me TSocket timeouts. > Checking the error log of Cassandra servers, all 3 nodes had this and they > all became unresponsive! Not sure how to reproduce this but a restart of all > 3 nodes fixed the issue: > > ERROR [COMMIT-LOG-WRITER] 2010-08-09 11:30:27,722 CassandraDaemon.java (line > 82) Uncaught exception in thread Thread[COMMIT-LOG-WRITER,5,main] > java.lang.AssertionError > at > org.apache.cassandra.db.commitlog.CommitLogHeader$CommitLogHeaderSerializer.serialize(CommitLogHeader.java:157) > at > org.apache.cassandra.db.commitlog.CommitLogHeader.writeCommitLogHeader(CommitLogHeader.java:124) > at > org.apache.cassandra.db.commitlog.CommitLogSegment.writeHeader(CommitLogSegment.java:70) > at > org.apache.cassandra.db.commitlog.CommitLogSegment.write(CommitLogSegment.java:103) > at > org.apache.cassandra.db.commitlog.CommitLog$LogRecordAdder.run(CommitLog.java:521) > at > org.apache.cassandra.db.commitlog.PeriodicCommitLogExecutorService$1.runMayThrow(PeriodicCommitLogExecutorService.java:52) > at > org.apache.cassandra.utils.WrappedRunnable.run(WrappedRunnable.java:30) > at java.lang.Thread.run(Thread.java:636) > > > -Arya > -- Jonathan Ellis Project Chair, Apache Cassandra co-founder of Riptano, the source for professional Cassandra support http://riptano.com
