cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nirmal Ranganathan (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CASSANDRA-1189) Refactor streaming
Date Wed, 21 Jul 2010 18:30:55 GMT

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

Nirmal Ranganathan commented on CASSANDRA-1189:
-----------------------------------------------

Yes, combining 1 & 2 will work out, reducing that extra message.

We'll have the following:
- Stream (The response part, it doesn't use a verb currently and will not going forward too)
- StreamRequest (Reuse the Stream_Request verb)
- StreamStatus (Reuse Stream_Finished verb)


> 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.


Mime
View raw message