cassandra 1.0.8 memory usage

Hi guys, I am running a mini cluster with 6 nodes, recently we see very frequent ParNewGC on two nodes. It takes 200 - 800 ms on average, sometimes it takes 5 seconds. You know, hte ParNewGC is stop-of-wolrd GC and our client throws SocketTimeoutException every 3 minutes. I checked the load, it

Re: cassandra 1.0.8 memory usage

to 20% Thanks, Daniel On Fri, Oct 12, 2012 at 2:02 AM, Rob Coli rc...@palominodb.com wrote: On Wed, Oct 10, 2012 at 11:04 PM, Daniel Woo daniel.y@gmail.com wrote: I am running a mini cluster with 6 nodes, recently we see very frequent ParNewGC on two nodes. It takes 200 - 800 ms

resultSetMetadata returned by PreparedStatement for sum(int) should be bigint

Hi guys, I am trying to calculate sum(int) with a prepared statement. The problem is that I have many rows to sum up, the result could be a bigint, however cassandra java driver receives the metadata as int. My current workaround is to change the column type to bigint. What's the best practice

LWT and non-LWT mixed

The document explains you cannot mix them http://docs.datastax.com/en/archived/cassandra/2.2/cassandra/dml/dmlLtwtTransactions.html But what happens under the hood if I do? e.g, DELETE INSERT ... IF NOT EXISTS The coordinator has 4 steps to do the second statement (INSERT) 1.

Re: Does NTP affects LWT's ballot UUID?

his event is ... > > On Tue, Oct 10, 2017 at 9:07 AM, Daniel Woo <daniel.y@gmail.com> > wrote: > >> Hi guys, >> >> The ballot UUID should be monotonically increasing on each coordinator, >> but the UUID in cassandra is version 1 (timestamp based), what

Does NTP affects LWT's ballot UUID?

Hi guys, The ballot UUID should be monotonically increasing on each coordinator, but the UUID in cassandra is version 1 (timestamp based), what happens if the NTP service adjusts system clock while a two phase paxos prepare/commit is in progress? -- Thanks & Regards, Daniel

What happens to coordinators and clients when I drain a node?

Hi guys, I have two questions about the drain status. The doc says when a node is drained it stops accepting new requests and flush memtable to disk. Does it stops accepting new requests immediately or wait for the majority of the nodes to gossip about the DRAINED status? If it stops accepting