cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel Meyer (JIRA)" <>
Subject [jira] [Created] (CASSANDRA-6028) Default sstable output size not respected when running sstablesplit
Date Fri, 13 Sep 2013 17:57:52 GMT
Daniel Meyer created CASSANDRA-6028:

             Summary: Default sstable output size not respected when running sstablesplit
                 Key: CASSANDRA-6028
             Project: Cassandra
          Issue Type: Bug
         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
            Priority: Minor
             Fix For: 2.0, 1.2.9

Run sstablesplit -h:

usage: sstablessplit [options] <filename> [<filename>]*
Split the provided sstables files in sstables of maximum provided file
size (see option --size).
Options are:
    --debug         display stack traces
 -h,--help          display this help message
    --no-snapshot   don't snapshot the sstables before splitting
 -s,--size <size>   maximum size in MB for the output sstables (default:
 -v,--verbose       verbose output

>From the help message we expect the default size to be 50 MB.

repro steps:

supply any sstable of any size to sstablesplit but leave out the --size option.
Expected: should split sstable into 50MB sstables
Pre-split sstables snapshotted into snapshot pre-split-1379086801768
Error splitting SSTableReader(path='./Keyspace1/Standard1/Keyspace1-Standard1-ic-15-Data.db'):
Invalid target size for SSTables, must be > 0 (got: 0)

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:

View raw message