[jira] [Commented] (CASSANDRA-8321) SStablesplit behavior changed

["Joshua McKenzie (JIRA)" <ji...@apache.org>]

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

Joshua McKenzie commented on CASSANDRA-8321:
--------------------------------------------

+1, though we might want to add in a test for sstablesplit w/abort() path instead of finish() just to be safe.  abort() code looks like it shouldn't give us any problems while isOffline but may as well while we're here.

> SStablesplit behavior changed
> -----------------------------
>
>                 Key: CASSANDRA-8321
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-8321
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Philip Thompson
>            Assignee: Marcus Eriksson
>            Priority: Minor
>             Fix For: 2.1.3
>
>         Attachments: 0001-ccm-fix-file-finding.patch, 0001-remove-tmplink-for-offline-compactions.patch
>
>
> The dtest sstablesplit_test.py has begun failing due to an incorrect number of sstables being created after running sstablesplit.
> http://cassci.datastax.com/job/cassandra-2.1_dtest/559/changes#detail1
> is the run where the failure began.
> In 2.1.x, the test expects 7 sstables to be created after split, but instead 12 are being created. All of the data is there, and the sstables add up to the expected size, so this simply may be a change in default behavior. The test runs sstablesplit without the --size argument, and the default has not changed, so it is unexpected that the behavior would change in a minor point release.



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