cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benedict (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-9681) Memtable heap size grows and many long GC pauses are triggered
Date Tue, 30 Jun 2015 08:21:04 GMT


Benedict commented on CASSANDRA-9681:

40m? That's unreasonable, but I'm afraid I'm not sure what you can do to make it faster. It
should be pretty quick, really. It's possible the -F option makes it slower, by taking a suboptimal

It looks like the space used grows slowly but steadily in your previous graphs. Perhaps to
avoid the issue of another healthy heap dump and other problems, we should wait until the
line is consistently above the healthy mark...

In the meantime, those other log files (during the most severe period) could be helpful.

> Memtable heap size grows and many long GC pauses are triggered
> --------------------------------------------------------------
>                 Key: CASSANDRA-9681
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>         Environment: C* 2.1.7, Debian Wheezy
>            Reporter: mlowicki
>            Assignee: Benedict
>            Priority: Critical
>             Fix For: 2.1.x
>         Attachments: cassandra.yaml,,,,
> C* 2.1.7 cluster is behaving really bad after 1-2 days. {{}}
jumps to 7 GB (
on 3/6 nodes in each data center and then there are many long GC pauses. Cluster is using
default heap size values ({{-Xms8192M -Xmx8192M -Xmn2048M}})
> Before C* 2.1.5 memtables heap size was basically constant ~500MB (
> After restarting all nodes is behaves stable for 1-2days. Today I've done that and long
GC pauses are gone (~18:00
The only pattern we've found so far is that long GC  pauses are happening basically at the
same time on all nodes in the same data center - even on the ones where memtables heap size
is not growing.
> Cliffs on the graphs are nodes restarts.
> Used memory on boxes where {{AllMemtabelesHeapSize}} grows, stays at the same level -
> Replication factor is set to 3.

This message was sent by Atlassian JIRA

View raw message