[
https://issues.apache.org/jira/browse/CASSANDRA-4047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yuki Morishita updated CASSANDRA-4047:
--------------------------------------
Attachment: 4047-2.0-wip.txt
[~brandon.williams] Attached is streaming 2.0 version of your patch.
As you pointed out, streaming session do not store ks/cf names and ranges. It
is just what part of SSTables to where.
So I let callback keep a map of destination to ks/cf/ranges and do whatever
need to do to clean up after stream session succeed.
Is this good enough to hand back to you?
> 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)
