You may want to try upgrading to 3.11.3 instead which has some memory leaks
fixes.
On Tue, Aug 28, 2018 at 9:59 AM, Mun Dega wrote:
> I am surprised that no one else ran into any issues with this version. GC
> can't catch up fast enough and there is constant Full GC taking place.
>
> The result
Ma, did you try what Mohamadreza suggested? Have a such a large heap means
you are getting a ton of stuff that needs full GC.
On Tue, Aug 28, 2018 at 4:31 AM Pradeep Chhetri
wrote:
> You may want to try upgrading to 3.11.3 instead which has some memory
> leaks fixes.
>
> On Tue, Aug 28, 2018 at
Hello Folks,
I've an virtualized environment running with VMware where Cassandra is humming
on NFS mounted storage. As the application load increases ,they increase number
of nodes in data center however writes are getting slower, nodes are flapping
and application complains in write performan
You may want to check if coincidentally you’re having expired cells in heap. GC
log should be able to tell you OR look for tombstones in system.log file. See
your compactions are under control and normal. This may not be related to
upgrade at all!
From: Pradeep Chhetri [mailto:prad...@stashaw
Hello,
nodetool tablestats my_kespace
returns SSTable Compression Ratio -1.0
Can someone explain, what does -1.0 mean?
Regards,
Vitaliy
-
To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org
For additional commands, e-
Compression ratio is ratio of compression to its original size - smaller is
better; see it like compressed/uncompressed
1 would mean no change in size after compression!
-Original Message-
From: Vitaliy Semochkin [mailto:vitaliy...@gmail.com]
Sent: Tuesday, August 28, 2018 12:03 PM
To
Hello,
I've noticed that after a stress test that does only inserts a
commitlog content exceeds data dir 20 times.
What can be cause of such behavior?
Running nodetool compact did not change anything.
Regards,
Vitaliy
-
To unsu
Thank you ZAIDI, can you please explain why mentioned ratio is negative?
On Tue, Aug 28, 2018 at 8:18 PM ZAIDI, ASAD A wrote:
>
> Compression ratio is ratio of compression to its original size - smaller is
> better; see it like compressed/uncompressed
> 1 would mean no change in size after compr
Try to use iSCSI , also play around with mount configurations for the filesystem
On Tue, Aug 28, 2018 at 8:46 AM ZAIDI, ASAD A wrote:
>
> Hello Folks,
>
>
>
> I’ve an virtualized environment running with VMware where Cassandra is
> humming on NFS mounted storage. As the application load increase
Hi everyone,
couple of days ago I have upgraded Cassandra from 3.11.2 to 3.11.3 and I
see that repair time is practically doubled. Does someone else experience
the same regression ?
Regards,
Maxim.
10 matches
Mail list logo