cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marcus Eriksson (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (CASSANDRA-10831) Fix the way we replace sstables after anticompaction
Date Fri, 18 Dec 2015 09:10:46 GMT

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

Marcus Eriksson edited comment on CASSANDRA-10831 at 12/18/15 9:09 AM:
-----------------------------------------------------------------------

For the record, we have successfully done repair with anticompaction on a cluster with 500GB/node
and vnodes with the patch


was (Author: krummas):
For the record, we have successfully done repair with anticompaction on a cluster with 500GB/node
and vnodes 

> Fix the way we replace sstables after anticompaction
> ----------------------------------------------------
>
>                 Key: CASSANDRA-10831
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-10831
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Marcus Eriksson
>            Assignee: Marcus Eriksson
>             Fix For: 2.1.x
>
>
> We have a bug when we replace sstables after anticompaction, we keep adding duplicates
which causes leveled compaction to fail after. Reason being that LCS does not keep its sstables
in a {{Set}}, so after first compaction, we will keep around removed sstables in the leveled
manifest and that will put LCS in an infinite loop as it tries to mark non-existing sstables
as compacting



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

Mime
View raw message