>
> Increasing new heap size generally helps when you're seeing a lot of
> promotion - if you're not seeing long major GCs, are you seeing a lot of
> promotion from eden to old gen?
> You don't typically set -Xmn (new heap size) when using G1GC
Nope not really
> currently using JVM_OPTS="$JVM_OP
On 2017-07-07 07:26 (-0700), Pranay akula wrote:
> Lately i am seeing some select queries timing out, data modelling to blame
> for but not in a situation to redo it.
>
> Does increasing heap will help ??
>
> currently using 1GB new_heap, I analysed the GC logs not having any issues
> with ma
...@gmail.com]
Sent: Friday, July 07, 2017 11:47 AM
To: user@cassandra.apache.org
Cc: ZAIDI, ASAD A
Subject: Re: READ Queries timing out.
Thanks ZAIDI,
Using C++ driver doesn't have tracing with driver so executing those from
cqlsh. when i am tracing i am getting below error, i increased
--re
> It can happen at the client side because of connection pool queue too full
> (which is likely due to response time from the cluster/coordinate nodes).
>
> And the issues at the cluster side could be due to several reasons.
>
> E.g. your query has to scan through too many tombstones
A"
Date: Friday, July 7, 2017 at 9:45 AM
To: "user@cassandra.apache.org"
Subject: RE: READ Queries timing out.
>> I analysed the GC logs not having any issues with major GC's
If you don’t have issues on GC , than why do you want to [tune] GC
parameters ?
Thanks ZAIDI,
The problem is the tracing queries are also getting timed out, so not sure
how to troubleshoot.
Does increasing new_heap will help reads ?? what other param's i can tune,
so that i can identify the issue.
Thanks
Pranay.
On Fri, Jul 7, 2017 at 10:45 AM, ZAIDI, ASAD A wrote:
>
>> I analysed the GC logs not having any issues with major GC's
If you don’t have issues on GC , than why do you want to [tune] GC
parameters ?
Instead focus on why select queries are taking time.. may be take a look on
their trace?
From: Pranay akula [mailto:pranay.akula2...@gmail.
