[
https://issues.apache.org/jira/browse/CASSANDRA-10990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15172237#comment-15172237
]
Yuki Morishita commented on CASSANDRA-10990:
--------------------------------------------
Current check requires to have disk space of 2 * transferring SSTable, so for
example we need to receive a SSTable file of 100GB at bootstrap then we need
200GB of free space beforehand on bootstrapping node, even we may write 2 MB of
buffer file. I think {{totalSize + Integer.MAX_VALUE}} can do the job here.
We want to do
bq. An alternative approach is to overwrite the spill file for each partition,
so we need disk space proportional to the max partition size
with the cap.
bq. but this will probably cause write amplification.
We don't need to overwrite for every partition, we can apply cap here too.
Implementation may become a bit complicated though. WDYT?
bq. I set the initial capacity to 32KB, do you think this is sufficient or do
you prefer 128KB ?
32 is fine, users can change through system prop if they really need to.
BTW, you can use {{Integer.getInteger}} instead of
{{Integer.parseInt(System.getProperty)}}.
> Support streaming of older version sstables in 3.0
> --------------------------------------------------
>
> Key: CASSANDRA-10990
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10990
> Project: Cassandra
> Issue Type: Bug
> Components: Streaming and Messaging
> Reporter: Jeremy Hanna
> Assignee: Paulo Motta
>
> In 2.0 we introduced support for streaming older versioned sstables
> (CASSANDRA-5772). In 3.0, because of the rewrite of the storage layer, this
> became no longer supported. So currently, while 3.0 can read sstables in the
> 2.1/2.2 format, it cannot stream the older versioned sstables. We should do
> some work to make this still possible to be consistent with what
> CASSANDRA-5772 provided.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
