Return-Path: X-Original-To: apmail-cassandra-user-archive@www.apache.org Delivered-To: apmail-cassandra-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 1525111DF5 for ; Fri, 2 May 2014 07:30:23 +0000 (UTC) Received: (qmail 94384 invoked by uid 500); 2 May 2014 07:30:19 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 93406 invoked by uid 500); 2 May 2014 07:30:15 -0000 Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@cassandra.apache.org Delivered-To: mailing list user@cassandra.apache.org Received: (qmail 93398 invoked by uid 99); 2 May 2014 07:30:14 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 02 May 2014 07:30:14 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=RCVD_IN_DNSWL_NONE,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy includes SPF record at spf.trusted-forwarder.org) Received: from [80.67.31.93] (HELO smtprelay05.ispgateway.de) (80.67.31.93) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 02 May 2014 07:30:09 +0000 Received: from [217.86.247.221] (helo=[172.17.2.42]) by smtprelay05.ispgateway.de with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.68) (envelope-from ) id 1Wg7uk-000596-La for user@cassandra.apache.org; Fri, 02 May 2014 09:29:46 +0200 Message-ID: <5363496A.8000006@dg6obo.de> Date: Fri, 02 May 2014 09:29:46 +0200 From: Jan Kesten User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20131103 Icedove/17.0.10 MIME-Version: 1.0 To: user@cassandra.apache.org Subject: repair -pr does not return Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Df-Sender: amFuQGRnNm9iby5kZQ== X-Virus-Checked: Checked by ClamAV on apache.org Hello together, I'm running a cassandra cluster with 2.0.6 and 6 nodes. As far as I know, routine repairs are still mandatory for handling tombstones - even I noticed that the cluster now does a "snapshot-repair" by default. Now my cluster is running a while and has a load of about 200g per node - running a "nodetool repair -pr" on one of the nodes seems to run forever, right now it's running for 2 complete days and does not return. Any suggestions? Thanks in advance, Jan