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 Thu, 21 Nov 2013 20:39:36 GMT

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

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

Actually I meant I couldn't get the ks/cf name and ranges on the client (bulk loader) side,
though I guess looking at this we can *almost* get there, except we need to them for onFailure
and I'm not quite sure how to do that.

> 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
>             Fix For: 2.0.3
>
>         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.1#6144)

Mime
View raw message