Well we are able to do the tracing under normal load, but not yet able to
turn on tracing on demand during heavy load from client side(due to hard to
predict traffic pattern).
under normal load we saw most of the time query spent (in one particular
row we focus on) between
merging data from
Maybe you should try to lower your read repair probability?
—
Sent from Mailbox
On Sat, Nov 15, 2014 at 9:40 AM, Jimmy Lin y2klyf+w...@gmail.com wrote:
Well we are able to do the tracing under normal load, but not yet able to
turn on tracing on demand during heavy load from client side(due
hi Jen,
interesting idea, but I thought read repair happen in background, and so
won't affect the actual read request calling from real client. ?
On Sat, Nov 15, 2014 at 1:04 AM, Jens Rantil jens.ran...@tink.se wrote:
Maybe you should try to lower your read repair probability?
—
Sent from
yes, already found...via the QueryOptions
2014-11-15 1:28 GMT+01:00 Tyler Hobbs ty...@datastax.com:
Cassandra itself does not have default consistency levels. These are only
configured in the driver.
On Fri, Nov 14, 2014 at 8:54 AM, Adil adil.cha...@gmail.com wrote:
Hi,
We are using two
So I think there are some operations in CQL WRT sets/maps that aren’t
supported yet or at least not very well documented.
For example, you can set the TTL on individual set members, but how do you
read the writetime() ?
normally on a column I can just
SELECT writetime(foo) from my_table;
but …
I have two tasks trying to each insert into a table. The only problem is
that I only want one to win, and then never perform that operation again.
So my idea was to use the set append support in Cassandra to attempt to
append to the set and if we win, then I can perform my operation. The
