You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Tyler Hobbs (JIRA)" <ji...@apache.org> on 2014/10/07 17:53:34 UTC

[jira] [Commented] (CASSANDRA-7616) sstablesplit creates new sstable when size is less than split size

    [ https://issues.apache.org/jira/browse/CASSANDRA-7616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14162026#comment-14162026 ] 

Tyler Hobbs commented on CASSANDRA-7616:
----------------------------------------

[~jchs86] if all sstables get skipped, the call to {{cfs.getDataTracker().markCompacting(sstables)}} throws an AssertionError.  The tool can just exit if {{sstables}} is empty.

> sstablesplit creates new sstable when size is less than split size
> ------------------------------------------------------------------
>
>                 Key: CASSANDRA-7616
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-7616
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Tools
>            Reporter: Tyler Hobbs
>            Priority: Minor
>              Labels: lhf, triaged
>             Fix For: 2.1.1
>
>         Attachments: CASSANDRA_7616.patch
>
>
> If you run sstablesplit on an sstable that is smaller than the split size, it still creates a new (duplicate) sstable.  It should just leave the existing sstable in place and do nothing.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)