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 1E873E859 for ; Sun, 17 Feb 2013 22:12:53 +0000 (UTC) Received: (qmail 56720 invoked by uid 500); 17 Feb 2013 22:12:50 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 56700 invoked by uid 500); 17 Feb 2013 22:12:50 -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 56691 invoked by uid 99); 17 Feb 2013 22:12:50 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 17 Feb 2013 22:12:50 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of marco.matarazzo@hexkeep.com designates 209.85.215.181 as permitted sender) Received: from [209.85.215.181] (HELO mail-ea0-f181.google.com) (209.85.215.181) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 17 Feb 2013 22:12:42 +0000 Received: by mail-ea0-f181.google.com with SMTP id i13so2116220eaa.12 for ; Sun, 17 Feb 2013 14:12:20 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:content-type:mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references:to:x-mailer :x-gm-message-state; bh=O2jp56c23jTf2jcKvctF8AcoOXVp9ybmj78ppJQR8H8=; b=oyETI9l0NsyoXXj2Cnwk3ctTExGy1lxEqZF9gAmQYahrJWhJL6UDtM7YuM+TuaXzC7 NHi4D2wr6TI1Rd4UgwuEjH2ZA23AG8JgtnPvf9PhrS9vrd1bPVJzFsLFWBX9v140rXa8 iTUbrhAGwXVBlyf0NiQEX3g0N82zDMks1I2ALBhnUbLcn3fHyzEpzlZhgRbPt0Lw9qRi Lk7oM4HefiDj8UAKJYQh/1NKE/NXGLloTlh93ZOsKAVzpOo8El22X9dSG3oGUb3GLlGr LXHXJpy2uCc4zSG0NTzRTIusR7vqvk72TMETz5zHrWR/oUCV5o/TdE244BQC7Q0SzpCn gBfw== X-Received: by 10.14.207.73 with SMTP id m49mr37045101eeo.24.1361139140641; Sun, 17 Feb 2013 14:12:20 -0800 (PST) Received: from [192.168.2.10] (net-93-65-139-5.cust.dsl.vodafone.it. [93.65.139.5]) by mx.google.com with ESMTPS id s3sm24849132eem.4.2013.02.17.14.12.18 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 17 Feb 2013 14:12:19 -0800 (PST) Content-Type: text/plain; charset=windows-1252 Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\)) Subject: Re: nodetool repair with vnodes From: Marco Matarazzo In-Reply-To: <40ED42F4-50A1-4391-B815-6AD2680FF042@thelastpickle.com> Date: Sun, 17 Feb 2013 23:12:16 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: <012EF9CC-6672-400A-A720-FF6127613768@hexkeep.com> References: <40ED42F4-50A1-4391-B815-6AD2680FF042@thelastpickle.com> To: user@cassandra.apache.org X-Mailer: Apple Mail (2.1499) X-Gm-Message-State: ALoCoQleNuOJAAVcE7t8YWn/z06LtdULiih5T/sFTmdCMfhmzByERaK7IB7/pJFjNHcNms98ual6 X-Virus-Checked: Checked by ClamAV on apache.org >> So, to me, it's like the "nodetool repair" command is running always = on the same single node and repairing everything. > If you use nodetool repair without the -pr flag in your setup (3 nodes = and I assume RF 3) it will repair all token ranges in the cluster.=20 That's correct, 3 nodes and RF 3. Sorry for not specifying it in the = beginning. So, running it periodically on just one node is enough for cluster = maintenance ? Does this depends on the fact that every vnode data is = related with the previous and next vnode, and this particular setup = makes this enough as it cover every physical node? Also: running it with -pr does output: [2013-02-17 12:29:25,293] Nothing to repair for keyspace 'system' [2013-02-17 12:29:25,301] Starting repair command #2, repairing 1 ranges = for keyspace keyspace_test [2013-02-17 12:29:28,028] Repair session = 487d0650-78f5-11e2-a73a-2f5b109ee83c for range = (-9177680845984855691,-9171525326632276709] finished [2013-02-17 12:29:28,028] Repair command #2 finished =85 that, as far as I can understand, works on the first vnode on the = specified node, or so it seems from the output range. Am I right? Is = there a way to run it only for all vnodes on a single physical node ? Thank you! -- Marco Matarazzo