cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Piotr Kołaczkowski (JIRA) <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-4047) Bulk hinting
Date Mon, 29 Dec 2014 19:59:14 GMT

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

Piotr Kołaczkowski commented on CASSANDRA-4047:
-----------------------------------------------

Yeah, you're right. It will be of higher priority when we add support for bulk writes in Spark.

> Bulk hinting
> ------------
>
>                 Key: CASSANDRA-4047
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-4047
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Brandon Williams
>              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)

Mime
View raw message