[
https://issues.apache.org/jira/browse/CASSANDRA-4047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13614070#comment-13614070
]
Brandon Williams commented on CASSANDRA-4047:
---------------------------------------------
I think I have a plan here that can avoid the hell of making MS multi-port.
Akin to how shuffle works with creating a 'schedule' for transfers, upon
failure we can insert the range that failed into a system table on a replica
that succeeded via thrift, and when the node recovers we can repair the range.
> 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: Brandon Williams
> Fix For: 2.0
>
>
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
