cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brandon Williams (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-4047) Bulk hinting
Date Wed, 20 Jun 2012 22:37:42 GMT

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

Brandon Williams commented on CASSANDRA-4047:
---------------------------------------------

The tricky part is, who stores the hint?  Since it's a non-member doing the streaming... I
guess it could just choose some other target at random, but by the time it does that the sstable
might already be compacted away.
                
> Bulk hinting
> ------------
>
>                 Key: CASSANDRA-4047
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-4047
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Brandon Williams
>            Assignee: Brandon Williams
>             Fix For: 1.2
>
>
> With the introduction of the BulkOutputFormat, there may be cases where someone would
like to tolerate node failures and have the job complete, but afterwards since we streamed
they have to repair or rely on read repair.  We don't currently have any way of hinting streams,
but a node could take a snapshot before acknowledging the stream session, then remember to
send the files in the snapshot to the unavailable nodes when they come back up.  This isn't
quite ideal since of course the node may have compacted these files, however it's much simpler
than any sort of key tracking at this scale.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message