It's a compatibility bug in b3. Moving all the nodes to b3 will fix it, or upgrading the new ones to 0.7 branch instead of b3 will too.
On Fri, Nov 19, 2010 at 8:40 AM, Damick, Jeffrey <jeffrey.dam...@neustar.biz> wrote: > > On upgrade of one of our nodes to beta3 from beta2, startup it gives: > > .... > INFO [main] 2010-11-19 14:06:09,482 Mx4jTool.java (line 68) mx4j > successfuly loaded > INFO [main] 2010-11-19 14:06:09,509 CassandraDaemon.java (line 77) Binding > thrift service to /0.0.0.0:9160 > INFO [main] 2010-11-19 14:06:09,512 CassandraDaemon.java (line 91) Using > TFramedTransport with a max frame size of 15728640 bytes. > INFO [main] 2010-11-19 14:06:09,515 CassandraDaemon.java (line 119) > Listening for thrift clients... > ERROR [Thread-4] 2010-11-19 14:06:09,518 AbstractCassandraDaemon.java (line > 89) Fatal exception in thread Thread[Thread-4,5,main] > java.lang.AssertionError > at > org.apache.cassandra.net.MessagingService.receive(MessagingService.java:386) > at > org.apache.cassandra.net.IncomingTcpConnection.run(IncomingTcpConnection.java:84) > ERROR [Thread-5] 2010-11-19 14:06:09,520 AbstractCassandraDaemon.java (line > 89) Fatal exception in thread Thread[Thread-5,5,main] > java.lang.AssertionError > at > org.apache.cassandra.net.MessagingService.receive(MessagingService.java:386) > at > org.apache.cassandra.net.IncomingTcpConnection.run(IncomingTcpConnection.java:84) > > > We’re still running other beta2 nodes in the cluster, am I configuring > something wrong or is this a compatibility issue? > > thanks > -- Jonathan Ellis Project Chair, Apache Cassandra co-founder of Riptano, the source for professional Cassandra support http://riptano.com
