Michael Bock created CASSANDRA-5656: ---------------------------------------
Summary: NPE in SSTableNamesIterator Key: CASSANDRA-5656 URL: https://issues.apache.org/jira/browse/CASSANDRA-5656 Project: Cassandra Issue Type: Bug Affects Versions: 1.2.4 Environment: SUSE Linux Enterprise Server 10, SP3. IBM Java 1.6.0 SR 13 Reporter: Michael Bock When adding a new node to our cluster we occasionally get the following error in the cassandra system log: 2013-06-18T07:13:18:942|ERROR|ReadStage:30|org.apache.cassandra.service.CassandraDaemon|Exception in thread Thread[ReadStage:30,5,main] java.lang.NullPointerException at java.util.TreeSet.iterator(TreeSet.java:230) at org.apache.cassandra.db.columniterator.SSTableNamesIterator.read(SSTableNamesIterator.java:163) at org.apache.cassandra.db.columniterator.SSTableNamesIterator.<init>(SSTableNamesIterator.java:64) at org.apache.cassandra.db.filter.NamesQueryFilter.getSSTableColumnIterator(NamesQueryFilter.java:81) at org.apache.cassandra.db.filter.QueryFilter.getSSTableColumnIterator(QueryFilter.java:68) at org.apache.cassandra.db.CollationController.collectTimeOrderedData(CollationController.java:133) at org.apache.cassandra.db.CollationController.getTopLevelColumns(CollationController.java:65) at org.apache.cassandra.db.ColumnFamilyStore.getTopLevelColumns(ColumnFamilyStore.java:1357) at org.apache.cassandra.db.ColumnFamilyStore.getColumnFamily(ColumnFamilyStore.java:1214) at org.apache.cassandra.db.ColumnFamilyStore.getColumnFamily(ColumnFamilyStore.java:1126) at org.apache.cassandra.db.Table.getRow(Table.java:347) at org.apache.cassandra.db.SliceByNamesReadCommand.getRow(SliceByNamesReadCommand.java:64) at org.apache.cassandra.db.ReadVerbHandler.doVerb(ReadVerbHandler.java:44) at org.apache.cassandra.net.MessageDeliveryTask.run(MessageDeliveryTask.java:56) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:908) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:931) at java.lang.Thread.run(Thread.java:738) The same exception then occurs repeatedly every few milliseconds and the node is not working. Calls via the API are timing out. -- 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