cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas Steinmaurer (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-11155) Scrub/Cleanup block snapshots
Date Tue, 13 Jun 2017 11:08:02 GMT


Thomas Steinmaurer commented on CASSANDRA-11155:

We are seeing the same issue with Cassandra 2.1.15. We have an hourly snapshot CRON job in
place and recently extended our production cluster from 6 to 9 nodes, thus executing nodetool
cleanup on the older 6 nodes one by one. What we see is:
* Accummulating CROND based nodetool snapshot processes according to the Linux process list
* Host CPU usage ~ 95% with a m4.xlarge in AWS, using 4 concurrent_compactors and the default
16 MB/s compaction threshold

> Scrub/Cleanup block snapshots
> -----------------------------
>                 Key: CASSANDRA-11155
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Compaction
>         Environment: Linux Ubuntu hosts, Cassandra 2.1.12
>            Reporter: Victor Igumnov
>         Attachments: cass-scrub-threaddump.bz2
> I have noticed that when running the cleanup or scrub process on Cassandra it prevents
nodetool from taking a snapshot. The snapshot process essentially blocks until the scrub or
cleanup is complete. I am not exactly sure if this is intended behavior. 
> For the record, this observed behavior does not apply to repairs and major compactions.

This message was sent by Atlassian JIRA

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

View raw message