You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Stu Hood (JIRA)" <ji...@apache.org> on 2010/06/18 18:23:25 UTC

[jira] Issue Comment Edited: (CASSANDRA-1189) Refactor streaming

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

Stu Hood edited comment on CASSANDRA-1189 at 6/18/10 12:22 PM:
---------------------------------------------------------------

AntiEntropyService.RepairSession in trunk and 0.6 only has a local view, so it can't know when other nodes have finished streaming data for repairs: it only blocks until streaming has started.

EDIT: After 1190, what this requirement will boil down to is "make StreamIn.requestRanges return a Future".

      was (Author: stuhood):
    If streaming sessions/files were given unique ids, it would be helpful for repairs as well.

AntiEntropyService.RepairSession in trunk and 0.6 only has a local view, so it can't know when other nodes have finished streaming data for repairs: it only blocks until streaming has started. If streaming sessions had unique ids, the destination node could block for notification that a particular stream id had finished before indicating that the repair was finished.
  
> 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: Gary Dusbabek
>            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.