Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Fri, 18 Mar 2016 14:16:33 +0000 (UTC)
From: "Aleksey Yeschenko (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12546328.1331680691000.59813.1458310593730@Atlassian.JIRA>
In-Reply-To: <JIRA.12546328.1331680691000@Atlassian.JIRA>
References: <JIRA.12546328.1331680691000@Atlassian.JIRA>
 <JIRA.12546328.1331680691252@arcas>
Subject: [jira] [Commented] (CASSANDRA-4047) Bulk hinting
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Aleksey Yeschenko commented on CASSANDRA-4047:
----------------------------------------------

[~pkolaczk] Please reopen if anything has changed since Dec 2014 and this is now relevant for Spark.

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