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 63E908A85 for ; Thu, 18 Aug 2011 23:58:01 +0000 (UTC) Received: (qmail 26228 invoked by uid 500); 18 Aug 2011 23:57:59 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 26128 invoked by uid 500); 18 Aug 2011 23:57:58 -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 26120 invoked by uid 99); 18 Aug 2011 23:57:58 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 18 Aug 2011 23:57:58 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of meatforums@gmail.com designates 209.85.216.44 as permitted sender) Received: from [209.85.216.44] (HELO mail-qw0-f44.google.com) (209.85.216.44) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 18 Aug 2011 23:57:52 +0000 Received: by qwc23 with SMTP id 23so2162590qwc.31 for ; Thu, 18 Aug 2011 16:57:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; bh=b+1cikSzvy0C+f/rzzXWk1CP5OcWVq7ppEW3H/eS/Wc=; b=Kj9ExV6jePyJ9GllXn4e81npiClJGytuQ2sJLgh4y5rh4b+FvnmTYSf0nvDEJ+Rhx3 YIkt+sc8ybl/SC0yhZNwVLeKgjqfPZnIfsTOpGH4qz7sBr1TQ7EsYIenjA69yxL0aQZF DMSrQW7uuRTzrQJGBfJDXKpZqbMa4s1PC2fqY= MIME-Version: 1.0 Received: by 10.224.10.17 with SMTP id n17mr1140778qan.347.1313711851107; Thu, 18 Aug 2011 16:57:31 -0700 (PDT) Received: by 10.229.28.80 with HTTP; Thu, 18 Aug 2011 16:57:31 -0700 (PDT) Date: Thu, 18 Aug 2011 16:57:31 -0700 Message-ID: Subject: Need to maintenance on a cassandra node, are there problems with this process From: Anand Somani To: user@cassandra.apache.org Content-Type: multipart/alternative; boundary=bcaec5196e2138f78d04aad0604e --bcaec5196e2138f78d04aad0604e Content-Type: text/plain; charset=ISO-8859-1 Hi, version - 0.7.4 cluster size = 3 RF = 3. data size on a node ~500G I want to do some disk maintenance on a cassandra node, so the process that I came up with is - drain this node - back up the system data space - rebuild the disk partition - copy data from another node - copy data from the backed up system data - restart node - run nodetool repair Is this process sane. Never done a read repair on this cluster before, is that a problem? Should I run it per CF? Would it help if I did this before bringing the node down? Any pointers, things to worry about. Thanks Anand --bcaec5196e2138f78d04aad0604e Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi,

version - 0.7.4
cluster size =3D 3
RF =3D 3.
data size = on a node ~500G

I want to do some disk maintenance on a cassandra no= de, so the process that I came up with is

drain this node

back up the system data space

rebuild the disk partition

co= py data from another node

copy data from the backed up system data<= /li>

restart node

run nodetool repair

Is this process s= ane. Never done a read repair on this cluster before, is that a problem? Sh= ould I run it per CF? Would it help if I did this before bringing the node = down?

Any pointers, things to worry about.

Thanks
Anand
--bcaec5196e2138f78d04aad0604e--