Growth of garbage collector

[hna...@gmail.com]

Used Heap is constantly inflating, garbage collector does not work, when I press run gc from the mancenter, garbage collector starts and the used head decreases from 10GB to 2GB, is there a way to automate this?

[Neil Stevenson]

 How big is the heap ? Which GC algorithm are you using and how is it configured ?

  

 And much more important, is heap usage causing any problems such as a long pause ?

 

 It appears you have 2GB of data, which shouldn't cause problems for a modern JVM. 

 Also "Run GC" is only a suggestion to the Garbage Collector, that it can ignore, so it's not a solution.

[hna...@gmail.com]

Hi Neil, Thank you for your quick reply and time. I appreciate it.

Here is the configuration for our hazelcast nodes.

<hazelcast xmlns="http://www.hazelcast.com/schema/config" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.hazelcast.com/schema/config http://www.hazelcast.com/schema/config/hazelcast-config-3.12.xsd">

    <map name="default">
        <backup-count>0</backup-count>
        <async-backup-count>0</async-backup-count>
        <read-backup-data>false</read-backup-data>
    </map>    
    <queue name="default">
        <backup-count>0</backup-count>
        <async-backup-count>0</async-backup-count>
    </queue>
    <group>
        <name>gridbox</name>
        <password>????????</password>
    </group>
    <instance-name>HZ_GridBox</instance-name>
    <management-center enabled="true" scripting-enabled="true">
        <url>http://???????????:8080/hazelcast-mancenter</url>
    </management-center>
    <properties>
        <property name="hazelcast.diagnostics.metric.level">info</property>
        <property name="hazelcast.diagnostics.enabled">true</property>
        <property name="hazelcast.max.no.heartbeat.seconds">120</property>
        <property name="hazelcast.backpressure.enabled">true</property>
        <property name="hazelcast.client.allow.invocations.when.disconnected">true</property>
        <property name="hazelcast.client.invocation.timeout.seconds">300</property>
       
       
    </properties>
    <network>
        <port auto-increment="false">5701</port>
        <reuse-address>false</reuse-address>
        <join>
            <multicast enabled="false">
            </multicast>
            <tcp-ip enabled="true">
                <member-list>
                    <member>????????</member>
                    <member>???????</member>
                    <member>??????</member>
                </member-list>
            </tcp-ip>
        </join>
    </network>
    <!--
    <queue name="DataPersistanceQueue">
        <max-size>8000</max-size>
        <backup-count>0</backup-count>
    </queue>
    -->
</hazelcast>

3 Mayıs 2022 Salı tarihinde saat 14:57:08 UTC+3 itibarıyla ne...@hazelcast.com şunları yazdı:

[Neil Stevenson]

Hi,

 (1) You're using 3.12

  The password is ignored if you don't have the security module.

  3.12 is an old version, it would be advisable to upgrade if you can, but it's irrelevant to the problem.

 (2) Someone has set hazelcast.max.no.heartbeat.seconds

  These are generally expert level settings, so you may have a local expert you can ask, if you can find who added this property

 (3) What problem is heap usage causing ?

Neil

--
You received this message because you are subscribed to the Google Groups "Hazelcast" group.
To unsubscribe from this group and stop receiving emails from it, send an email to hazelcast+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/hazelcast/f16eb14c-6df2-401f-84dd-c5625a6fb6a6n%40googlegroups.com.

This message contains confidential information and is intended only for the individuals named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission. If verification is required, please request a hard-copy version. -Hazelcast

[Neil Stevenson]

Thanks. 

What problem do you see occurring ?

On Wed, 4 May 2022 at 17:55, hna...@gmail.com <hna...@gmail.com> wrote:

java -server -Xmx16g -Xms12g -verbose:gc -XX:+PrintGCDetails -XX:+PrintGCTimeStamps -XX:+PrintGCDateStamps -Xloggc:C:/GridBox/Services/Hazelcast/gc.log -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=C:/GridBox/Services/Hazelcast -Djava.util.logging.config.file=C:/GridBox/Services/Hazelcast/logging.properties.txt -cp "hazelcast-3.12.1.jar;." HzWithXML

4 Mayıs 2022 Çarşamba tarihinde saat 12:19:28 UTC+3 itibarıyla hna...@gmail.com şunları yazdı:

--
You received this message because you are subscribed to a topic in the Google Groups "Hazelcast" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/hazelcast/mxg6tq2ZIMY/unsubscribe.
To unsubscribe from this group and all its topics, send an email to hazelcast+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/hazelcast/c137a2c4-d0e6-44e8-9b34-467fc9e53b30n%40googlegroups.com.

[hna...@gmail.com]

Hi Neil, 

Thank you for your support. 

1- The memory size of the members is up to 13GB. It empties after running Garbage collected. 

This situation causes the problem in the system to access the nodes. the system does not become stable without restarting the nodes.

We will set the hazelcast.max.no.heartbeat.seconds value to 300 seconds as in the default. In addition, do we need to make any changes in the configuration structure below?

hazelcast.max.no.heartbeat.seconds

java -server -Xmx16g -Xms12g -verbose:gc -XX:+PrintGCDetails -XX:+PrintGCTimeStamps -XX:+PrintGCDateStamps -Xloggc:C:/GridBox/Services/Hazelcast/gc.log -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=C:/GridBox/Services/Hazelcast -Djava.util.logging.config.file=C:/GridBox/Services/Hazelcast/logging.properties.txt -cp "hazelcast-3.12.1.jar;." HzWithXML

Best Regards

Hasan Nayman

5 Mayıs 2022 Perşembe tarihinde saat 09:42:51 UTC+3 itibarıyla ne...@hazelcast.com şunları yazdı:

[Neil Stevenson]

 There's nothing in what you're shared so far that proves it's heap to blame.

 If you're sure it's that, why use such a large heap ? 

 Seems you have plenty headroom

Neil

You received this message because you are subscribed to the Google Groups "Hazelcast" group.

To unsubscribe from this group and stop receiving emails from it, send an email to hazelcast+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/hazelcast/73711ac3-dfb7-464e-bb06-131bcab6569en%40googlegroups.com.