cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Joshua McKenzie (JIRA)" <>
Subject [jira] [Issue Comment Deleted] (CASSANDRA-11996) SSTableSet.CANONICAL can miss sstables
Date Wed, 29 Jun 2016 12:00:42 GMT


Joshua McKenzie updated CASSANDRA-11996:
    Comment: was deleted

(was: bq. Shouldn't we only return the canonical sstables that are passed into select as a
true, argh.. this approach wont work at all - the sstables passed in do not contain the original
version of the sstable, JUST the early opened one when we are finishing up the compaction...

bq. In the test, don't we need to call DatabaseDescriptor.setSSTablePreempiveOpenIntervalInMB()
no, this happens since we always open an "early" sstable when finishing writing an sstable
- the {{setPreemptive...}} i had in the finally clause was a copy and paste leftover)

> SSTableSet.CANONICAL can miss sstables
> --------------------------------------
>                 Key: CASSANDRA-11996
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Marcus Eriksson
>            Assignee: Marcus Eriksson
>            Priority: Critical
>             Fix For: 3.0.x, 3.x
> There is a race where we might miss sstables in SSTableSet.CANONICAL when we finish up
a compaction.
> Reproducing unit test pushed [here|]

This message was sent by Atlassian JIRA

View raw message