[ https://issues.apache.org/jira/browse/CASSANDRA-6026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13766730#comment-13766730 ]
Daniel Meyer commented on CASSANDRA-6026: ----------------------------------------- This issue is probably related to CASSANDRA-6027; however, the actual behavior is different so two bugs filed. > NPE when running sstablesplit on valid sstable > ---------------------------------------------- > > Key: CASSANDRA-6026 > URL: https://issues.apache.org/jira/browse/CASSANDRA-6026 > Project: Cassandra > Issue Type: Bug > Environment: Environment: java version "1.7.0_40" > Java(TM) SE Runtime Environment (build 1.7.0_40-b43) > Java HotSpot(TM) 64-Bit Server VM (build 24.0-b56, mixed mode) > (Sun jvm on mac) > Reporter: Daniel Meyer > Assignee: Sylvain Lebresne > Fix For: 1.2.9 > > > #create cluster > ccm create --cassandra-version git:cassandra-1.2 test > ccm populate -n 1 > ccm start > #run stress > ccm node1 stress -n 10000000 -o insert > ccm node1 compact > cd ~/.ccm/test/node1/data > ../bin/sstablesplit -n 100 > ./Keyspace1/Standard1/Keyspace1-Standard1-ic-16-Data.db > #Expected > single large sstable should be split into multiple sstables with max size 100 > MB > #Actual > ERROR 10:14:06,992 Error in ThreadPoolExecutor > java.lang.NullPointerException > at > org.apache.cassandra.io.sstable.SSTableDeletingTask.run(SSTableDeletingTask.java:70) > at > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) > at java.util.concurrent.FutureTask.run(FutureTask.java:262) > at > java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178) > at > java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > at java.lang.Thread.run(Thread.java:724) > Notes: It seems like the split occurs and can be recompacted. > Last known commit where split was working on 1.2 branch: > 47b2cd6620894bf0c4c4584036eab49a2e14a50e > Have not bisected further. > sstablesplit is also broken on 2.0 branch; however, it fails differently. > Filing separate bug on that. -- 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