cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Paulo Motta (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-13687) Abnormal heap growth and CPU usage during repair.
Date Tue, 25 Jul 2017 01:09:00 GMT


Paulo Motta commented on CASSANDRA-13687:

Thanks! I wonder if that could be related to CASSANDRA-13052, that for some reason is causing
the merkle tree comparison on the coordinator to be more costly in some edge case (cc []
since I'm not familiar with that change).

A heap dump or snapshot from jvisualvm during repair would probably help identify the primary

> Abnormal heap growth and CPU usage during repair.
> -------------------------------------------------
>                 Key: CASSANDRA-13687
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Stanislav Vishnevskiy
>         Attachments: 3.0.14cpu.png, 3.0.14heap.png, 3.0.14.png, 3.0.9heap.png, 3.0.9.png
> We recently upgraded from 3.0.9 to 3.0.14 to get the fix from CASSANDRA-13004
> Sadly 3 out of the last 7 nights we have had to wake up due Cassandra dying on us. We
currently don't have any data to help reproduce this, but maybe since there aren't many commits
between the 2 versions it might be obvious.
> Basically we trigger a parallel incremental repair from a single node every night at
1AM. That node will sometimes start allocating a lot and keeping the heap maxed and triggering
GC. Some of these GC can last up to 2 minutes. This effectively destroys the whole cluster
due to timeouts to this node.
> The only solution we currently have is to drain the node and restart the repair, it has
worked fine the second time every time.
> I attached heap charts from 3.0.9 and 3.0.14 during repair.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message