Return-Path: Delivered-To: apmail-cassandra-user-archive@www.apache.org Received: (qmail 31858 invoked from network); 27 Sep 2010 16:09:51 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 27 Sep 2010 16:09:51 -0000 Received: (qmail 52404 invoked by uid 500); 27 Sep 2010 16:09:49 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 52284 invoked by uid 500); 27 Sep 2010 16:09:48 -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 52275 invoked by uid 99); 27 Sep 2010 16:09:48 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 27 Sep 2010 16:09:48 +0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=FREEMAIL_FROM,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of jbellis@gmail.com designates 209.85.215.172 as permitted sender) Received: from [209.85.215.172] (HELO mail-ey0-f172.google.com) (209.85.215.172) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 27 Sep 2010 16:09:44 +0000 Received: by eyd10 with SMTP id 10so1947914eyd.31 for ; Mon, 27 Sep 2010 09:09:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=QDynPoDJCzAFjE6908IUUUl7fxzS/HX6v7pwbgoFYao=; b=AQzb7OhMHXSPjqCkguYNJn+RW0La+LaY9XdMm7GG7MMv5uYGlPVuybEZXZR4/VlrwK HZwANJB29mz0nn2giAch+ddc64MesqkYc1GkN/iwbmyYW7sRYJv85uFEfbrwO7BEkfhd 2OEuqny8m2A5ZJyqr8f/x7R+eumT19p2lAasA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=vFf+h3N4n+T0pWgG+5QabZZYgrXI+zrWd2MuIfF13nft0yotk5Omb3N3CownUzT3AC f8+I+AQ6w6VkDEpCc3I3KLaCnzXnX2WqtNLlG1UOR/CrOuNi+wfEbom/X+kJvpdJ39u7 8+JI8OH0tJJp0PqiYFqwy6sOPtOjWqAlVfcTo= MIME-Version: 1.0 Received: by 10.103.40.1 with SMTP id s1mr1070965muj.4.1285603755373; Mon, 27 Sep 2010 09:09:15 -0700 (PDT) Received: by 10.220.188.131 with HTTP; Mon, 27 Sep 2010 09:09:14 -0700 (PDT) In-Reply-To: References: Date: Mon, 27 Sep 2010 09:09:14 -0700 Message-ID: Subject: Re: Best strategy for adding new nodes to the cluster From: Jonathan Ellis To: user Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable I strongly recommend not running live on Small nodes. So in your case I would recommend starting up Large instances with raid0'd disks, shut down cassandra on the Small ones, rsync to the Large, and start up on Large. On Mon, Sep 27, 2010 at 6:46 AM, Utku Can Top=E7u wrote= : > Hi All, > > We're currently running a cassandra cluster with Replication Factor 3, > consisting of 4 nodes. > > The current situation is: > > - The nodes are all identical (AWS small instances) > - Data directory is in the partition (/mnt) which has 150G capacity and e= ach > node has around 90 GB load, so 60 G free space per node is left. > > So adding a new node to the cluster will seem to cause problems for us. I > think the node which will stream the data to the new bootstrapping node, > will not have enough disk space for anticompacting its data. > > What should be the best practice for such scenarios? > > Regards, > > Utku > --=20 Jonathan Ellis Project Chair, Apache Cassandra co-founder of Riptano, the source for professional Cassandra support http://riptano.com