[
https://issues.apache.org/jira/browse/CASSANDRA-10495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14950983#comment-14950983
]
Jonathan Shook commented on CASSANDRA-10495:
--------------------------------------------
What if the streaming protocol were enhanced to allow sending nodes to provide
an offer manifest, blocking until the receiver responded with a preferred
ordering and grouping. Does this help address any of the planning issues better?
> Improve the way we do streaming with vnodes
> -------------------------------------------
>
> Key: CASSANDRA-10495
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10495
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Marcus Eriksson
> Fix For: 3.x
>
>
> Streaming with vnodes usually creates a large amount of sstables on the
> target node - for example if each source node has 100 sstables and we use
> num_tokens = 256, the bootstrapping (for example) node might get 100*256
> sstables
> One approach could be to do an on-the-fly compaction on the source node,
> meaning we would only stream out one sstable per range. Note that we will
> want the compaction strategy to decide how to combine the sstables, for
> example LCS will not want to mix sstables from different levels while STCS
> can probably just combine everything
> cc [~yukim]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
