From user-return-35843-apmail-cassandra-user-archive=cassandra.apache.org@cassandra.apache.org Fri Aug 9 01:03:58 2013 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 D373A10D20 for ; Fri, 9 Aug 2013 01:03:58 +0000 (UTC) Received: (qmail 67575 invoked by uid 500); 9 Aug 2013 01:03:56 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 67555 invoked by uid 500); 9 Aug 2013 01:03:56 -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 67547 invoked by uid 99); 9 Aug 2013 01:03:56 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 09 Aug 2013 01:03:56 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of mohitanchlia@gmail.com designates 209.85.160.54 as permitted sender) Received: from [209.85.160.54] (HELO mail-pb0-f54.google.com) (209.85.160.54) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 09 Aug 2013 01:03:49 +0000 Received: by mail-pb0-f54.google.com with SMTP id ro12so4129065pbb.27 for ; Thu, 08 Aug 2013 18:03:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=references:mime-version:in-reply-to:content-type :content-transfer-encoding:message-id:cc:from:subject:date:to; bh=9hPhDnQ+U9QpfAFRUx1c8H8FSEkEQhoj9pFpxJfSv4I=; b=rFqqZfl9AFSWJsmioLuoqXObb12x8DRW81bMatQ168S5oHYxQd69lymADo8DxKOnEh oNXkQ/lx4LYp9nyR7LzD7YIhW6wrXrkXV6YAKjsyccm+PIu0FVT8rJBB5CIvb0sK9yVs fOx4J2bskWOayJZYJ8d+U5QY2FXGblAK8/FYGQTn5fmRH/gPY4bXABLS5q1oJh7AiFYM fkqQidQ1NyB8kekitBXnzM1eqd+LNybjfxMqppjVFNyfhOTkxL3nM8choAyiJnmcVZ4J C5temXay+mEAqa1ArSfMfpCTpCiPvI3JftYRGbW6yJFFXVkgHM6WU5zBWvb/Y7BSb8Yl CBkA== X-Received: by 10.68.162.36 with SMTP id xx4mr8720029pbb.47.1376010208460; Thu, 08 Aug 2013 18:03:28 -0700 (PDT) Received: from [192.168.1.136] (cpe-50-113-71-136.san.res.rr.com. [50.113.71.136]) by mx.google.com with ESMTPSA id ts6sm16857567pbc.12.2013.08.08.18.03.26 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 08 Aug 2013 18:03:27 -0700 (PDT) References: <707A7CFA945C43CDA59339E07765EF38@addthis.com> Mime-Version: 1.0 (1.0) In-Reply-To: Content-Type: multipart/alternative; boundary=Apple-Mail-02C1E4AF-FD44-4ABD-8D43-74034B28299B Content-Transfer-Encoding: 7bit Message-Id: <82BD18E0-E716-46AD-B9D4-F8C34D0FA78B@gmail.com> Cc: "user@cassandra.apache.org" X-Mailer: iPhone Mail (10B350) From: Mohit Anchlia Subject: Re: Cassandra nodetool repair question Date: Thu, 8 Aug 2013 18:03:23 -0700 To: "user@cassandra.apache.org" X-Virus-Checked: Checked by ClamAV on apache.org --Apple-Mail-02C1E4AF-FD44-4ABD-8D43-74034B28299B Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable But node might be streaming data as well, in that case only option is to res= tart node that started streaming operation Sent from my iPhone On Aug 8, 2013, at 5:56 PM, Andrey Ilinykh wrote: > nodetool repair just triggers repair procedure. You can kill nodetool afte= r start, it doesn't change anything. To stop repair you have to use nodetool= stop VALIDATION|COMPACTION >=20 >=20 > Thank you, >=20 > Andrey >=20 >=20 >=20 > On Thu, Aug 8, 2013 at 1:00 PM, Andy Losey wrote: >> Afternoon, >>=20 >> We are noticing nodetool repair processes are not completing after a week= s worth of time, and have resulted in some Cassandra nodes having more than o= ne process running do to cron scheduled. We are also chasing some performanc= e degradation after upgrading all nodes to version 1.2.8 last Friday and wou= ld like to resolve this multiple repairs running at once issue in an effort t= o troubleshoot our performance issues. >>=20 >> We'd like to know more about what is happening with the repair option. Is= there a way to gracefully terminate them or any adverse affect to killing t= he processes we should look out for? >>=20 >> Thanks, >> --=20 >> Andy L >=20 --Apple-Mail-02C1E4AF-FD44-4ABD-8D43-74034B28299B Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 7bit
But node might be streaming data as well, in that case only option is to restart node that started streaming operation

Sent from my iPhone

On Aug 8, 2013, at 5:56 PM, Andrey Ilinykh <ailinykh@gmail.com> wrote:

nodetool repair just triggers repair procedure. You can kill nodetool after start, it doesn't change anything. To stop repair you have to use nodetool stop VALIDATION|COMPACTION


Thank you,

  Andrey



On Thu, Aug 8, 2013 at 1:00 PM, Andy Losey <andrew@addthis.com> wrote:
Afternoon,

We are noticing nodetool repair processes are not completing after a weeks worth of time, and have resulted in some Cassandra nodes having more than one process running do to cron scheduled. We are also chasing some performance degradation after upgrading all nodes to version 1.2.8 last Friday and would like to resolve this multiple repairs running at once issue in an effort to troubleshoot our performance issues.

We'd like to know more about what is happening with the repair option. Is there a way to gracefully terminate them or any adverse affect to killing the processes we should look out for?

Thanks,
-- 
Andy L


--Apple-Mail-02C1E4AF-FD44-4ABD-8D43-74034B28299B--