cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <j...@apache.org>
Subject [jira] Updated: (CASSANDRA-648) findSuitableEndPoint not returning closest endPoint
Date Sat, 19 Dec 2009 23:18:18 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jonathan Ellis updated CASSANDRA-648:
-------------------------------------

    Attachment: 648.patch

For efficiency, I'd prefer to make sortByProximity work in-place as its name suggests.

But we need the non-in-place for the Multimaps we have.

So here is a patch w/ two versions, the one leveraging the other of course.

> findSuitableEndPoint not returning closest endPoint
> ---------------------------------------------------
>
>                 Key: CASSANDRA-648
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-648
>             Project: Cassandra
>          Issue Type: Bug
>    Affects Versions: 0.5
>            Reporter: Chris Goffinet
>            Assignee: Chris Goffinet
>             Fix For: 0.5
>
>         Attachments: 0001-Returned-the-sorted-endpoints-properly-for-CASSANDRA.patch,
648.patch
>
>
> After we switched everything over to Rackaware, I was noticing queries still taking 80ms+.
We run in multiple datacenter's and I had a suspicion that it was just connecting to a node
on east coast. It looks like findSuitableEndPoint sorts endpoints, but does not use the returned
sorted endpoints when needing to return the final endpoint. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message