Return-Path: X-Original-To: apmail-cassandra-commits-archive@www.apache.org Delivered-To: apmail-cassandra-commits-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 155AF18D84 for ; Tue, 5 Jan 2016 22:42:45 +0000 (UTC) Received: (qmail 95835 invoked by uid 500); 5 Jan 2016 22:42:40 -0000 Delivered-To: apmail-cassandra-commits-archive@cassandra.apache.org Received: (qmail 95808 invoked by uid 500); 5 Jan 2016 22:42:40 -0000 Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cassandra.apache.org Delivered-To: mailing list commits@cassandra.apache.org Received: (qmail 95796 invoked by uid 99); 5 Jan 2016 22:42:39 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 05 Jan 2016 22:42:39 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id C50422C1F56 for ; Tue, 5 Jan 2016 22:42:39 +0000 (UTC) Date: Tue, 5 Jan 2016 22:42:39 +0000 (UTC) From: "Carl Yeksigian (JIRA)" To: commits@cassandra.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (CASSANDRA-10829) cleanup + repair generates a lot of logs MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CASSANDRA-10829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15083978#comment-15083978 ] Carl Yeksigian commented on CASSANDRA-10829: -------------------------------------------- I think we need to make {{finished}} thread-safe, since we're submitting those to the compaction executor, which may be multi-threaded. > cleanup + repair generates a lot of logs > ---------------------------------------- > > Key: CASSANDRA-10829 > URL: https://issues.apache.org/jira/browse/CASSANDRA-10829 > Project: Cassandra > Issue Type: Bug > Environment: 5 nodes on Cassandra 2.1.11 (on Debian) > Reporter: Fabien Rousseau > Assignee: Marcus Eriksson > Fix For: 2.1.x > > > One of our node generates a lot of cassandra logs (int the 10 MB/s) and CPU usage has increased (by a factor 2-3). > This was most probably triggered by a "nodetool snapshot" while a cleanup was already running on this node. > An example of those logs: > 2015-12-08 09:15:17,794 INFO [ValidationExecutor:689]ColumnFamilyStore.java:1923 Spinning trying to capture released readers [...] > 2015-12-08 09:15:17,794 INFO [ValidationExecutor:689]ColumnFamilyStore.java:1924 Spinning trying to capture all readers [...] > 2015-12-08 09:15:17,795 INFO [ValidationExecutor:689]ColumnFamilyStore.java:1923 Spinning trying to capture released readers [...] > 2015-12-08 09:15:17,795 INFO [ValidationExecutor:689]ColumnFamilyStore.java:1924 Spinning trying to capture all readers [...] > (I removed SSTableReader information because it's rather long... I can share it privately if needed) > Note that the date has not been changed (only 1ms between logs) > It should not generate that gigantic amount of logs :) > This is probably linked to: https://issues.apache.org/jira/browse/CASSANDRA-9637 -- This message was sent by Atlassian JIRA (v6.3.4#6332)