You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Jonathan Ellis (JIRA)" <ji...@apache.org> on 2014/12/16 23:56:14 UTC

[jira] [Commented] (CASSANDRA-4047) Bulk hinting

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

Jonathan Ellis commented on CASSANDRA-4047:
-------------------------------------------

Where do we go from here?  [~pkolaczk] is this important for your team?

> 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: Yuki Morishita
>              Labels: hints
>             Fix For: 3.0
>
>         Attachments: 4047-2.0-wip.txt, 4047-wip.txt
>
>
> 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 was sent by Atlassian JIRA
(v6.3.4#6332)