cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marcus Eriksson (JIRA)" <>
Subject [jira] [Updated] (CASSANDRA-8623) sstablesplit fails *randomly* with Data component is missing
Date Mon, 26 Jan 2015 07:47:34 GMT


Marcus Eriksson updated CASSANDRA-8623:
    Attachment: 0001-make-sure-we-finish-compactions-before-waiting-for-d.patch

[~aboudreault] could you test this patch? I have not been able to reproduce this myself

Patch just makes sure all compactions are finished before waiting for the deletion tasks

Same issue could be in offline cleanup and offline scrub

> sstablesplit fails *randomly* with Data component is missing
> ------------------------------------------------------------
>                 Key: CASSANDRA-8623
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Alan Boudreault
>            Assignee: Marcus Eriksson
>         Attachments: 0001-make-sure-we-finish-compactions-before-waiting-for-d.patch,
> 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:
> 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.
> 5. The first time, run ./ 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

View raw message