[
https://issues.apache.org/jira/browse/CASSANDRA-2388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13059334#comment-13059334
]
Mck SembWever commented on CASSANDRA-2388:
------------------------------------------
{quote}2) If we ARE in that situation, the "right" solution would be to send
the job to a TT whose local replica IS live, not to read the data from a
nonlocal replica. How can we signal that?{quote}To /really/ solve this issue
can we do the following?
In CFIF.getRangeMap() take out of each range any endpoints that are not alive.
A client connection already exists in this method. This filtering out of dead
endpoints wouldn't be difficult, and would move tasks *to* the data making use
of replica. This approach does need a new method in cassandra.thrift, eg
{{list<string> describe_alive_nodes()}}
> 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, 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
