[
https://issues.apache.org/jira/browse/CASSANDRA-1189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12890794#action_12890794
]
Gary Dusbabek commented on CASSANDRA-1189:
------------------------------------------
This looks good.
I think both approaches 1 and 2 can be combined if you're willing to throw in
pending file lists as part of the stream header when the source replies to the
initial stream request. When the destination gets that data (along with the
first stream), it can then request specific files that it now knows about.
If we can trust TCP I don't think we need checksums.
It sounds like we need three basic kinds of messages: request, response and
status?
> Refactor streaming
> ------------------
>
> Key: CASSANDRA-1189
> URL: https://issues.apache.org/jira/browse/CASSANDRA-1189
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Affects Versions: 0.7
> Reporter: Gary Dusbabek
> Assignee: Nirmal Ranganathan
> Priority: Critical
> Fix For: 0.7
>
>
> The current architecture is buggy because it makes the assumption that only
> one stream can be in process between two nodes at a given time, and stream
> send order never changes. Because of this, the ACK process gets fouled up
> when other services wish to stream files.
> The process is somewhat contorted too (request, initiate, initiate done,
> send).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
