Return-Path: Delivered-To: apmail-cassandra-user-archive@www.apache.org Received: (qmail 10739 invoked from network); 31 Mar 2011 02:12:54 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 31 Mar 2011 02:12:54 -0000 Received: (qmail 16957 invoked by uid 500); 31 Mar 2011 02:12:53 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 16935 invoked by uid 500); 31 Mar 2011 02:12:53 -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 16927 invoked by uid 99); 31 Mar 2011 02:12:53 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 31 Mar 2011 02:12:53 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of watanabe.maki@gmail.com designates 209.85.214.44 as permitted sender) Received: from [209.85.214.44] (HELO mail-bw0-f44.google.com) (209.85.214.44) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 31 Mar 2011 02:12:45 +0000 Received: by bwz13 with SMTP id 13so1525620bwz.31 for ; Wed, 30 Mar 2011 19:12:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:date:message-id:subject:from:to :content-type; bh=AFs2cTG25VcHAyXxpVdJVv+7YQIM5NwvmJi7MsnarM8=; b=g+eXLz5uNRDaUf47TdJhwEQbkzt34p+XTVD+YMe+8EE9ohdObGj3i3iDp4lO5DWlUw 5TGsEkTzUQsJOlDDNat7fxTVt9aEIZUue8gmPoUnOJ8GIDAQB5FKu8+jnmCV4xC1OH/c enGEg9l0oIaVfJNYA/DwmHwsGnFeuWeanu0Gw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=aZOzNs2HRSWBoFOD0SfG32ScrJWeIG2chI6pJ4QZhdbPN7j+3fhNQ9m9MO1O7hQMa5 jTzMMnMyNguRMGuDm132utzMhYEp3rt1TwTtRPDzbnG2VKCVsMddRPbkTwYZ/svWtxWD 4rgnt5ZZqkaXw81NvTm2owtsn74AyNd4Ei3bg= MIME-Version: 1.0 Received: by 10.204.233.14 with SMTP id jw14mr1889501bkb.40.1301537545156; Wed, 30 Mar 2011 19:12:25 -0700 (PDT) Received: by 10.204.49.85 with HTTP; Wed, 30 Mar 2011 19:12:25 -0700 (PDT) Date: Thu, 31 Mar 2011 11:12:25 +0900 Message-ID: Subject: Naming "issue" on nodetool repair command From: Maki Watanabe To: user Content-Type: text/plain; charset=ISO-8859-1 X-Virus-Checked: Checked by ClamAV on apache.org Woud you cassandra team think to add an alias name for nodetool "repair" command? I mean, the word "repair" scares some of people. When I say "we need to run nodetool repair regularly on cassandra nodes", they think "OH... Those are broken so often!". So if I can say it in more soft word, ex. "sync", "tune", or "harmonize", it will be better in impression. maki