Thank you all. Now I understand whether to use batch or asynchronous writes
really depends on use case. Till now batch writes work for me in a 8 nodes
cluster with over 500 million requests per day.
Cheers,
-Simon
From: Eric Stevens
Date: 2018-11-02 01:14
To: user
Subject: Re: A quick question
As far as I know, it's not possible to change it live. You have to create
a new "datacenter" with new hosts using the new num_tokens value, then
switch everything to use the new DC and tear down the old.
On Thu, Nov 1, 2018 at 6:16 PM Goutham reddy
wrote:
> Hi team,
> Can someone help me out I
Hi team,
Can someone help me out I don’t find anywhere how to change the numtokens
on a running nodes. Any help is appreciated
Thanks and Regards,
Goutham.
--
Regards
Goutham Reddy
I know this is the official recommendation, and has been for a while. I
highly recommend testing it for yourself though, as our own testing has
shown that for _most_ versions of Cassandra (not all), unlogged batch
meaningfully outperforms parallel execution of individual statements,
especially at
Hello everyone,
I have a problem with the hints in my cluster.
In fact, my cluster is composed of 5 nodes : 3 nodes in DC1 and 2 nodes in
DC2.
The size of the hints folder increases rapidly and it reaches nearly the
90% of the hard drive (50 Gb).
The test scenario is the following : I applied 1000
To dig a little deeper.
It sounds like JMX is just enabled for loopback, if JMX was
disabled/unreachable entirely, nodetool wouldn't work at all.
You will likely need to customize your Cassandra config to allow remote JMX
connections (though this does increase your attack surface and risk from a
Hi All,
Do we have any inbuilt features to log slow\resource heavy queries?
I tried to check data in system_traces.sessions to check current running
sessions but even that does not have any data.
I'm asking this because I can see 2 nodes in my cluster going Out Of Memory
multiple times but we'
Read this: https://docs.datastax.com/en/cql/3.3/cql/cql_reference/batch_r.html
Please use batch (any type of batch) for statements that only concerns a single
partition, otherwise it cause a lot of performance degradation on your cluster
and after a while throughput would be alot less than paral
Hi All,
What's the difference between logged batch and unlogged batch? I'm asking this
question it's because I'm seeing the below WARNINGs after a new app started
writting to the cluster.
WARNING in system.log:
Unlogged batch covering 135 partitions detected against table
[cargts.eventdata].
