cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jonathan Ellis <jbel...@gmail.com>
Subject Re: snitch & thrift
Date Thu, 16 Jun 2011 17:11:47 GMT
Seems like a more robust solution would be to implement
dynamic-snitch-like behavior in the client.  Hector has done this for
a few months now.
https://github.com/rantav/hector/blob/master/core/src/main/java/me/prettyprint/cassandra/connection/DynamicLoadBalancingPolicy.java

On Thu, Jun 16, 2011 at 9:12 AM, Ryan King <ryan@twitter.com> wrote:
> On Thu, Jun 16, 2011 at 6:11 AM, Terje Marthinussen
> <tmarthinussen@gmail.com> wrote:
>> Hi all!
>> Assuming a node ends up in GC land for a while, there is a good chance that
>> even though it performs terribly and the dynamic snitching will help you to
>> avoid it on the gossip side, it will not really help you much if thrift
>> still accepts requests and the thrift interface has choppy performance.
>> This makes me wonder if it is a potential idea with thrift only client mode
>> nodes.
>
> Those could GC too, albeit to a lesser degree.
>
>> I don't think I have seen that this exists today (or is it possible that I
>> have missed a way to configure that?), but it does not seem like a very hard
>> thing to make and could maybe be good in some usage patterns for the
>> datanode as well as the thrift side.
>
> It might be sometimes useful, but we can't really know without running
> some tests.
>
> -ryan
>



-- 
Jonathan Ellis
Project Chair, Apache Cassandra
co-founder of DataStax, the source for professional Cassandra support
http://www.datastax.com

Mime
View raw message