cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robbie Strickland (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-9938) Significant GC pauses
Date Thu, 30 Jul 2015 15:10:05 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-9938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Robbie Strickland updated CASSANDRA-9938:
-----------------------------------------
    Attachment: gc_log.txt

> Significant GC pauses
> ---------------------
>
>                 Key: CASSANDRA-9938
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-9938
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>         Environment: Ubuntu 14.04, Java 1.8.0u45
>            Reporter: Robbie Strickland
>              Labels: gc
>         Attachments: gc_log.txt
>
>
> We have an 18-node analytics cluster, running 2.1.7 patched with CASSANDRA-9662.  On
a couple of the nodes we are seeing very long GC pauses, especially in old gen.  Eventually
these nodes OOM:
> {code}
> ERROR [SharedPool-Worker-167] 2015-07-30 00:36:20,746 JVMStabilityInspector.java:94 -
JVM state determined to be unstable.  Exiting forcefully due to: java.lang.OutOfMemoryError:
Java heap space
> {code}
> We use G1 with the following settings:
> Max heap = 16G
> New size = 1.6G
> +UseTLAB
> +ResizeTLAB
> +PerfDisableSharedMem
> -UseBiasedLocking
> The nodes in question have average load profiles for the cluster, and caches are disabled
on all tables.  There is no obvious difference with the problematic nodes.  Unfortunately
we're currently getting an assertion error when trying to get a heap dump, or I would post
that.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message