[
https://issues.apache.org/jira/browse/CASSANDRA-2388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13057470#comment-13057470
]
Mck SembWever commented on CASSANDRA-2388:
------------------------------------------
bq. tlipcon says it comes back after 24h
just to be clear about my concerns.
this means a dead c* node will bring down a TT. In a hadoop cluster with 3
nodes this means for 24hrs you're lost 33% throughput. (If less than 10% of
hadoop jobs used CFIF i could well imagine some pissed customers). (What if you
have a temporarily problem with flapping c* nodes and you end up with a handful
of blacklisted TTs? etc etc etc).
All this when using a replica, any replica, could have kept things going
smoothly, the only slowdown being some of the data into CFIF had to go over the
network instead...
> ColumnFamilyRecordReader fails for a given split because a host is down, even
> if records could reasonably be read from other replica.
> -------------------------------------------------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-2388
> URL: https://issues.apache.org/jira/browse/CASSANDRA-2388
> Project: Cassandra
> Issue Type: Bug
> Components: Hadoop
> Affects Versions: 0.7.6, 0.8.0
> Reporter: Eldon Stegall
> Assignee: Jeremy Hanna
> Labels: hadoop, inputformat
> Fix For: 0.7.7, 0.8.2
>
> Attachments: 0002_On_TException_try_next_split.patch,
> CASSANDRA-2388-addition1.patch, CASSANDRA-2388.patch, CASSANDRA-2388.patch,
> CASSANDRA-2388.patch
>
>
> ColumnFamilyRecordReader only tries the first location for a given split. We
> should try multiple locations for a given split.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
