Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Tue, 20 Jan 2015 22:21:35 +0000 (UTC)
From: "Alan Boudreault (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12767650.1421293243000.128392.1421792495193@Atlassian.JIRA>
In-Reply-To: <JIRA.12767650.1421293243000@Atlassian.JIRA>
References: <JIRA.12767650.1421293243000@Atlassian.JIRA>
 <JIRA.12767650.1421293243845@arcas>
Subject: [jira] [Commented] (CASSANDRA-8623) sstablesplit fails *randomly*
 with Data component is missing
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Alan Boudreault commented on CASSANDRA-8623:
--------------------------------------------

I have been able to reproduce the issue using a single sstable and calling multiple sstablesplit. Question: what are the files created in system/compactions_in_progress?

> sstablesplit fails *randomly* with Data component is missing
> ------------------------------------------------------------
>
>                 Key: CASSANDRA-8623
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-8623
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Alan Boudreault
>            Assignee: Marcus Eriksson
>         Attachments: output.log
>
>
> I'm experiencing an issue related to sstablesplit. I would like to understand if I am doing something wrong or there is an issue in the split process. The process fails randomly with the following exception:
> {code}
> ERROR 02:17:36 Error in ThreadPoolExecutor
> java.lang.AssertionError: Data component is missing for sstable./tools/bin/../../data/data/system/compactions_in_progress-55080ab05d9c388690a4acb25fe1f77b/system-compactions_in_progress-ka-16
> {code}
> See attached output.log file. The process never stops after this exception and I've also seen the dataset growing indefinitely (number of sstables).  
> * I have not been able to reproduce the issue with a single sstablesplit command. ie, specifying all files with glob matching.
> * I can reproduce the bug if I call multiple sstablesplit one file at the time (the way ccm does)
> Here is the test case file to reproduce the bug:
> https://drive.google.com/file/d/0BwZ_GPM33j6KdVh0NTdkOWV2R1E/view?usp=sharing
> 1. Download the split_issue.tar.gz file. It includes latest cassandra-2.1 branch binaries.
> 2. Extract it
> 3. CD inside the use case directory
> 4. Download the dataset (2G) just to be sure we have the same thing, and place it in the working directory.
>    https://docs.google.com/uc?id=0BwZ_GPM33j6KV3ViNnpPcVFndUU&export=download
> 5. The first time, run ./test.sh. This will setup and run a test.
> 6. The next times, you can only run ./test --no-setup . This will only reset the dataset as its initial state and re-run the test. You might have to run the tests some times before experiencing it... but I'm always able with only 2-3 runs.


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