Re: Error code=1000

One or more of your nodes, depending on your replication factor, is not answering in time. Either they are down or have too much load that they are not able to answer every request before the timeout expires. On 31 Oct 2015 20:35, "Eduardo Alfaia" wrote: > Hi guys, > >

Re: CLUSTERING ORDER BY importance with ssd's

this probably depends on the number of rows we have but should one worry performance wise about this seek? or from how many rows should we worry about this? On 9 October 2015 at 21:26, Nate McCall wrote: > >> If I am selecting a range from the bottom of the partition,

CLUSTERING ORDER BY importance with ssd's

If I have a table CREATE TABLE status ( user text, time timestamp, status text, PRIMARY KEY (user, time)) WITH CLUSTERING ORDER BY (time ASC); adapted from http://www.datastax.com/dev/blog/row-caching-in-cassandra-2-1 This means at the top of the partition the oldest date

RE: Consistency Issues

Can you tell us how much time your gcs are taking? Do you see any especially long ones? On 1 Oct 2015 09:37, "Walsh, Stephen" wrote: > There is no load balancer in front of Cassandra, it’s in front of our > application. > > Everyone seems hung up on this point? But

Cassandra metrics custom reporter

Is anyone using a custom reporter to plugin to their own monitoring systems? ie one that does not use graphite or something for which a reporter exists. Any documentation on plugging this in? We have a custom reporter, it's been loaded and we see report method being called. But when we iterate