cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "T Jake Luciani (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (CASSANDRA-6296) Bootstrapping a new node should not require much compaction when leveled compaction is used
Date Mon, 11 Nov 2013 18:13:18 GMT

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

T Jake Luciani edited comment on CASSANDRA-6296 at 11/11/13 6:13 PM:
---------------------------------------------------------------------

But does it stream the same range from multiple replicas? or does it fetch different ranges?
 If it's the latter then this would still work with leveled, since there would be no overlap.


was (Author: tjake):
But does it stream the same range from multiple replicas? or does it fetch different ranges?
 If it's the former then this would still work with leveled, since there would be no overlap.

> Bootstrapping a new node should not require much compaction when leveled compaction is
used
> -------------------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-6296
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-6296
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: T Jake Luciani
>            Priority: Minor
>
> boostrapping a new node currently requires recompacting all data.  In the case of leveled
compaction we already have the data in non-overlapping levels. Since we stream from a single
host for a single range this shouldn't require any compaction if the sstable is > level
0



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message