Sure, if your analysis is correct we can either add the comment to
cassandray.yaml or NEWS.txt, or both.
Could you leave a comment with your analysis and suggestion to
CASSANDRA-11993? When Branimir is back from holiday he can probably confirm
easily if that's the case.
On Wed, Jun 22, 2016 at
Hi Stefania,
Thanks for the explanation - I think it may be more likely I'm hitting
MEMORY_USAGE_THRESHOLD
(file_cache_size_in_mb, which is 512mb by default), as the table itself is
very large (a couple TB over 12 nodes). In that case, due to the changes
outlined
[Moving to users list]
The most important thing will be to reduce your JVM heap size. Cassandra
will automatically reduce pool sizes as you do that. Disabling key cache
and row cache will help you get that even smaller.
On Tue, Jun 21, 2016 at 5:21 AM, Sumit Anvekar
What tool are you using to determine memory usage?
What OS are you using?
How much heap are you allocating to the JVM?
Cheers,
Christos Kalantzis
Sent from my mobile
On Jun 22, 2016 7:01 AM, "Sumit Anvekar" wrote:
> Hello,
> We are using Cassandra 3.0.7 version and
Hi there,
I would like to contribute to the wiki.
My wiki user name: SuraiyaKhan
Thanks.
Suraiya
Sorry the user name is: Suraiya Khan (ther is a space in between)
Thanks.
On Wed, Jun 22, 2016 at 12:43 AM, Suraiya Khan
wrote:
> Hi there,
> I would like to contribute to the wiki.
>
> My wiki user name: SuraiyaKhan
>
> Thanks.
>
> Suraiya
>
Hello,
We are using Cassandra 3.0.7 version and off late we see that 90% of memory
is occupied even though hard-drive is hardly used. We have a cluster of 5
nodes with 15 GB memory, 4 cores, 200 GB SSD.
We tried all kind of configurations through both YAML as well as table
based properties but
Hi Nimi
I am not familiar with how CASSANDRA-5863 uses the buffer pool yet, but I
do know how the buffer pool works
It has a local pool, which is thread local, and takes chunks from a global
pool. These are allocated off heap and aligned to the page cache
boundaries, see here