[CASSANDRA-6027] 'null' error when running sstablesplit on valid sstable

• Type: Bug
• Status: Resolved
• Priority: Normal
• Resolution: Fixed
• Fix Version/s: 2.0.1

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)

• Severity: Normal
• Assignee: Sylvain Lebresne
• Reporter: Daniel Meyer

Authors

Sylvain Lebresne

Reviewers

Aleksey Yeschenko

• Tester: Daniel Meyer
• Created: 13/Sep/13 17:49
• Updated: 16/Apr/19 09:32
• Resolved: 17/Sep/13 13:34

Description

ccm create --cassandra-version git:cassandra-2.0 test
ccm populate -n 1
ccm start

ccm node1 stress -n 10000000 -o insert
ccm node1 compact
cd ~/.ccm/test/node1/data
../bin/sstablesplit -s 100 ./Keyspace1/Standard1/Keyspace1-Standard1-jb-12-Data.db

Expected: single sstable should be split into multiple sstables

Got:
Pre-split sstables snapshotted into snapshot pre-split-1379088385051
Error splitting SSTableReader(path='./Keyspace1/Standard1/Keyspace1-Standard1-jb-12-Data.db'): null

running du -h on the large compacted sstable showed it to be 2.4GB

This is probably related to CASSANDRA-6026; however, it is different. In this bug the split does not occur, whereas in 6026 the split does occur though an error is thrown.