cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gary Dusbabek (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CASSANDRA-956) include stream request in Streaming status on destination node
Date Mon, 24 May 2010 15:01:28 GMT

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

Gary Dusbabek commented on CASSANDRA-956:
-----------------------------------------

I think the right place for keeping track of those things will be in StreamIn/OutManager.
 This gets a little invasive because we assume >0 pending files per manager instance in
several places.  In the case of waiting-on-compaction there should't be any pending files.

What you're saying makes sense, and is the right thing to do in trunk, but I don't like the
idea of doing it this way in 0.6.

> include stream request in Streaming status on destination node
> --------------------------------------------------------------
>
>                 Key: CASSANDRA-956
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-956
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>    Affects Versions: 0.6
>            Reporter: Jonathan Ellis
>            Assignee: Gary Dusbabek
>            Priority: Minor
>             Fix For: 0.6.2
>
>         Attachments: 0001-indicate-stream-sources-and-destinations-before-anti.patch,
956-indicate-waiting-nodes-0.6.txt
>
>
> Currently we log this as DEBUG in StreamIn but there is no other indication as to what
is happening on the destination node until anticompaction finishes and STREAM_INITATE arrives.

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