cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CASSANDRA-579) Add support to io.Streaming API for sending Streams
Date Fri, 07 May 2010 20:08:50 GMT

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

Jonathan Ellis commented on CASSANDRA-579:
------------------------------------------

Given how much cpu the compact part of anticompact chew up, Stu is right that we shouldn't
do that on the source node.  But we shouldn't do it on the target node, either, or more precisely,
we shouldn't do it as part of the stream operation and let the operator do it manually if
desired.

We should use the row index to figure out what parts of the source data files to stream over,
and send those chunks w/o deserializing anything.  On the target side, we should read the
keys but not deserialize anything else, and build the index + bloom filter from that.


> Add support to io.Streaming API for sending Streams
> ---------------------------------------------------
>
>                 Key: CASSANDRA-579
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-579
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Stu Hood
>            Priority: Critical
>             Fix For: 0.7
>
>
> The io.Streaming API currently requires a file on disk to stream, which means that bootstrap
and repairs need to perform an anti-compaction that writes a bunch of data to disk, only to
have it be deleted after the streaming has finished.
> EDIT: Deleted reference to using streaming as a client API: it wouldn't provide enough
benefit over using the BMT interface, due to fragility.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message