Hello All,
This is my first post here.
I noticed that Cassandra is pushing CQL3 more, it's even recommended to use
CQL3 for new projects instead of the Thrift API. I know that one can use
the compact storage to allow backward compatibility. And I know that CQL3
uses the new binary protocol instea
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.
On Sat, May 11, 2013 at 5:16 PM, Radim Kolar wrote:
> Dne 11.5.2013 21:36, Techy Teck napsal(a):
>
Dne 11.5.2013 21:36, Techy Teck napsal(a):
Does anyone using Astyanax client in production mainly for reading
purpose?
with cassandra 1.1, it has problems with 1.2.
Does anyone using Astyanax client in production mainly for reading purpose?
I'm using the JDBC driver to access Cassandra. I'm wondering if its
possible to iterate through a large number of records (e.g. to perform
maintenance on a large column family). I tried calling
Connection.createStatement(ResultSet.TYPE_FORWARD_ONLY,
ResultSet.CONCUR_READ_ONLY), but it times out, so
I`m running YCSB and sometimes, when the load is heavy, some nodes get down.
What does the first line of bin/nodetool ring output means? It has the same
token of the down node. For each down node, is it expected to be shown a
line like the first one (with most columns empty)?
Address DC
