cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marcus Eriksson (JIRA)" <>
Subject [jira] [Updated] (CASSANDRA-7460) Send source sstable level when bootstrapping or replacing nodes
Date Fri, 27 Jun 2014 09:43:24 GMT


Marcus Eriksson updated CASSANDRA-7460:

    Attachment: 0001-wip-keep-sstable-level-when-bootstrapping.patch

attaching 2.1-rebased patch for this

* send whether we can keep sstable levels in StreamInitMessage
* send sstable level in FileMessageHeader
* during bootstrap, only do STCS in L0 to avoid getting overlap in L1

Note that this still does not handle backwards compatibility as it is quite complicated to
fix and should probably be done in another ticket. 

My suggested fix is that when the stream initiator sends a StreamInitMessage with CURRENT_VERSION,
the receiver needs to reply with the max version that both nodes supports and the messages
are then sent using that version.

Another approach would be to figure out what version the remote node is before deciding on
streaming version, but that would mean we have to bump messaging version whenever we change
something in a stream message which we probably shouldn't.

WDYT [~yukim] ?

> Send source sstable level when bootstrapping or replacing nodes
> ---------------------------------------------------------------
>                 Key: CASSANDRA-7460
>                 URL:
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Marcus Eriksson
>            Assignee: Marcus Eriksson
>             Fix For: 2.1.1
>         Attachments: 0001-wip-keep-sstable-level-when-bootstrapping.patch
> When replacing or bootstrapping a new node we can keep the source sstable level to avoid
doing alot of compaction after bootstrap

This message was sent by Atlassian JIRA

View raw message