Update :
We also upgraded the Cassandra version from 2.1.16 to 3.11.2.
On Fri, Aug 21, 2020 at 9:02 AM Pushpendra Rajpoot <
pushpendra.nh.rajp...@gmail.com> wrote:
> Hi,
>
> We have updated the java minor version as given below.
>
> Older Java version "1.8.0_144"
> Newer Java version
Hi Cassandra Gurus,
Recently I captured a very interesting warning in the logs saying
2020-08-19 08:08:32.492
[cassandra-client-keytiles_data_webhits-nio-worker-2] WARN
com.datastax.driver.core.RequestHandler - Query '[3 bound values] select
* from visit_sess
ion_by_start_time_v4 where
Hi,
We have updated the java minor version as given below.
Older Java version "1.8.0_144"
Newer Java version "1.8.0_261"
Cassandra version : 2.1.16
Now we are getting below exception :
INFO [main] 2020-08-19 10:55:09,364 YamlConfigurationLoader.java:89 -
Configuration location:
You want to look for full or long GCs in the logs, as well as how much
total time it's spending on GCing as a percentage. Probably more the
latter, since you're not seeing long pauses with one core pegged and the
rest idle. G1 handles oversized heaps well, so it's worth bumping to
20-27GB just
Depending on your thread count, you can consider increasing the max native
transport threads and concurrent reads. But the keys to Cassandra are
pretty make good data, make good queries, and if you can't keep up, double
the cluster size. If you're following the documentation on heap size (1/2
RAM
Hi,
We have a cluster where if reads are increased 2-3 times suddenly then
cassandra cpu goes around 100% (We have 48 cpu machines with 128GB RAM) for
few nodes and cassandra becomes unresponsive .
We are on 3.11.5 and using G1GC with 16GB heap size.
When going through the system.logs and gc.log
