Re: RE: how to fix constantly getting out of memory (3.11)

[Jay Zhuang]

 Hi,
For CASSANDRA-13929, The patch is available for review. Anyone interested in 
reviewing it?
Thanks,Jay
On Tuesday, December 12, 2017, 5:02:14 AM PST, Steinmaurer, Thomas 
 wrote:  
 
 Hi,

if you are talking about on-heap troubles, then the following might be related 
in 3.11.x:
https://issues.apache.org/jira/browse/CASSANDRA-13929

Thomas

-Original Message-
From: Micha [mailto:mich...@fantasymail.de]
Sent: Dienstag, 12. Dezember 2017 09:24
To: dev@cassandra.apache.org
Subject: how to fix constantly getting out of memory (3.11)

Hi,

I have seven nodes, debian stretch with c*3.11, each with 2TB disk (500G free), 
32G Ram.
I have a keyspace with seven tables. At the moment the cluster doesn't work at 
all reliably. Every morning at least 2 nodes are shut down due to out of 
memory. Repair afterwards fails with "some repair failed".
I use G1 with 16G heap on 6 six nodes and cms with 8G heap on one node to see a 
difference. In munin it's easy to see a constantly rising memory consumption. 
There are no other services running. I cannot understand who is not releasing 
the memory.
Some tables have some big rows (as mentioned in my last mail to the list). Can 
this be a source of the memory consumption?

How do you track down this?  Is there memory which doesn't get released and 
accumulates over time? I have not yet debugged such gc/memory issues.

cheers
 Michael


-
To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
For additional commands, e-mail: dev-h...@cassandra.apache.org

The contents of this e-mail are intended for the named addressee only. It 
contains information that may be confidential. Unless you are the named 
addressee or an authorized designee, you may not copy or use it, or disclose it 
to anyone else. If you received it in error please notify us immediately and 
then destroy it. Dynatrace Austria GmbH (registration number FN 91482h) is a 
company registered in Linz whose registered office is at 4040 Linz, Austria, 
Freistädterstraße 313

-
To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
For additional commands, e-mail: dev-h...@cassandra.apache.org

  

RE: how to fix constantly getting out of memory (3.11)

[Steinmaurer, Thomas]

Hi,

if you are talking about on-heap troubles, then the following might be related 
in 3.11.x:
https://issues.apache.org/jira/browse/CASSANDRA-13929

Thomas

-Original Message-
From: Micha [mailto:mich...@fantasymail.de]
Sent: Dienstag, 12. Dezember 2017 09:24
To: dev@cassandra.apache.org
Subject: how to fix constantly getting out of memory (3.11)

Hi,

I have seven nodes, debian stretch with c*3.11, each with 2TB disk (500G free), 
32G Ram.
I have a keyspace with seven tables. At the moment the cluster doesn't work at 
all reliably. Every morning at least 2 nodes are shut down due to out of 
memory. Repair afterwards fails with "some repair failed".
I use G1 with 16G heap on 6 six nodes and cms with 8G heap on one node to see a 
difference. In munin it's easy to see a constantly rising memory consumption. 
There are no other services running. I cannot understand who is not releasing 
the memory.
Some tables have some big rows (as mentioned in my last mail to the list). Can 
this be a source of the memory consumption?

How do you track down this?  Is there memory which doesn't get released and 
accumulates over time? I have not yet debugged such gc/memory issues.

cheers
 Michael


-
To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
For additional commands, e-mail: dev-h...@cassandra.apache.org

The contents of this e-mail are intended for the named addressee only. It 
contains information that may be confidential. Unless you are the named 
addressee or an authorized designee, you may not copy or use it, or disclose it 
to anyone else. If you received it in error please notify us immediately and 
then destroy it. Dynatrace Austria GmbH (registration number FN 91482h) is a 
company registered in Linz whose registered office is at 4040 Linz, Austria, 
Freistädterstraße 313

-
To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
For additional commands, e-mail: dev-h...@cassandra.apache.org