)
Is this really correct?
I expected the result from the last select to be:
key | cluster | col
-+-+--
1 | 1 | null
(1 rows)
Regards,
Tommy
--
--
Marcin Pietraszek
part of gc logs requires
more attention?
On Tue, Jul 21, 2015 at 4:22 PM, Marcin Pietraszek
mpietras...@opera.com wrote:
Yup... it seems like it's gc fault
gc logs
2015-07-21T14:19:54.336+: 2876133.270: Total time for which
application threads were stopped: 0.0832030 seconds
2015-07-21T14
, 2015 at 9:18 AM, Jason Wee peich...@gmail.com wrote:
just a guess, gc?
On Mon, Jul 20, 2015 at 3:15 PM, Marcin Pietraszek mpietras...@opera.com
wrote:
Hello!
I've noticed a strange CPU utilisation patterns on machines in our
cluster. After C* daemon restart it behaves in a normal way, after
Hello!
I've noticed a strange CPU utilisation patterns on machines in our
cluster. After C* daemon restart it behaves in a normal way, after a
few weeks since a restart CPU usage starts to raise. Currently on one
of the nodes (screenshots attached) cpu load is ~4. Shortly before
restart load
Hi!
Is there any way to force cqlsh to display LexicalUUIDType values in
more readable way?
Currently it looks like a hex value mixed with some strange chars (^t @ * g=)
http://www.wepaste.com/kbl/
--
mp
Hi!
We have 56 node cluster with C* 2.0.13 + CASSANDRA-9036 patch
installed. Assume we have nodes A, B, C, D, E. On some irregular basis
one of those nodes starts to report that subset of other nodes is in
DN state although C* deamon on all nodes is running:
A$ nodetool status
UN B
DN C
DN D
UN
