incubator-cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Edward Capriolo <edlinuxg...@gmail.com>
Subject Re: Astyanax client in Production
Date Mon, 13 May 2013 20:49:49 GMT
Being token aware makes a big performance difference. We do that internally
with out client and it means a lot for 95 percentile time. If Astynax is
not vnode token aware and your using them you could see worse performance.

A long time "beef" with the client libraries is that they are always
chasing cassandra. Astyanax looked awesome and sexy new compared to hector
when it was released. But from what Radim is saying, it sounds like
Astyanax has the same problem hector does.

This is life in open source. I'm currently working on
https://issues.apache.org/jira/browse/CASSANDRA-5435 because ...I need
it.... That is what everything boils down to eventually. When netflix is
ready to switch to vnodes they will update their client because ...they
need it... :)


On Sun, May 12, 2013 at 3:15 AM, Radim Kolar <hsn@filez.com> wrote:

> Dne 12.5.2013 2:28, Techy Teck napsal(a):
>
>> I am running Cassandra 1.2.2 in production. What kind of problems you
>> talking about? Might be I get some root cause why I am seeing bad read
>> performance with Astyanax client in production cluster.
>>
> no support for full cassandra 1.2 feature set
> no/bad support for virtual nodes
> timeouts too often
>

Mime
View raw message