You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Daniel Meyer (JIRA)" <ji...@apache.org> on 2013/09/13 19:49:51 UTC
[jira] [Created] (CASSANDRA-6027) 'null' error when running sstable
split on valid sstable
Daniel Meyer created CASSANDRA-6027:
---------------------------------------
Summary: 'null' error when running sstable split on valid sstable
Key: CASSANDRA-6027
URL: https://issues.apache.org/jira/browse/CASSANDRA-6027
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)
Reporter: Daniel Meyer
Fix For: 2.0
ccm create --cassandra-version git:cassandra-1.2 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.
--
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