[
https://issues.apache.org/jira/browse/CASSANDRA-2388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13048727#comment-13048727
]
Mck SembWever edited comment on CASSANDRA-2388 at 6/14/11 11:22 AM:
--------------------------------------------------------------------
Won't the sorting still be wrong?
For the use-case above it will solve restricting to the correct datacenter, but
the sorting will still be based on proximity to the wrong node?
bq. I don't think it makes sense to send the client endpoint to this call since
the endpoint might not be a cassandra node.
It might not be an alive cassandra node, but it should be a cassandra node. It
comes from the split's list of endpoints. At least in this use-case, or are you
referring to general usage for this new api?
bq. It's a reasonable assumption that the endpoint it's talking to is local
enough to the client to use that.
I don't think so... The endpoint that it talks to is a completely random (just
the next endpoint listed in the split's list). This is why i think that such
sorting won't just be wrong but not even close. Does this make sense?
was (Author: michaelsembwever):
Won't the sorting still be wrong?
For the use-case above it will solve restricting to the correct datacenter, but
the sorting will still be based on proximity to the wrong node?
> 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
> Reporter: Eldon Stegall
> Assignee: Mck SembWever
> Labels: hadoop, inputformat
> Fix For: 0.8.1
>
> Attachments: 0002_On_TException_try_next_split.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
