Return-Path: Delivered-To: apmail-cassandra-user-archive@www.apache.org Received: (qmail 7356 invoked from network); 3 Jun 2010 06:22:10 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 3 Jun 2010 06:22:10 -0000 Received: (qmail 30836 invoked by uid 500); 3 Jun 2010 06:22:08 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 30824 invoked by uid 500); 3 Jun 2010 06:22:08 -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 30816 invoked by uid 99); 3 Jun 2010 06:22:08 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 03 Jun 2010 06:22:08 +0000 X-ASF-Spam-Status: No, hits=-0.1 required=10.0 tests=AWL,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of jbellis@gmail.com designates 74.125.82.44 as permitted sender) Received: from [74.125.82.44] (HELO mail-ww0-f44.google.com) (74.125.82.44) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 03 Jun 2010 06:22:03 +0000 Received: by wwb39 with SMTP id 39so3387389wwb.31 for ; Wed, 02 Jun 2010 23:21:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:mime-version:received:in-reply-to :references:from:date:message-id:subject:to:content-type :content-transfer-encoding; bh=7mrV+8ZyvviBBPWd5nPh59NwRXStWj0JFDwfbrZPtA8=; b=OmvZArBcS+5dEaXotsgAgIo1R7lD5gE0pkWAkLJ53j9gSVw/bKngZD2w5J23dSDAy8 fs5aTH6nohOSh+G1hKR4ffUWhe4zFQiwomTfFjJKwgKHNaZNF1XWqO45q7tF6MMpjfL7 AI2j90Jl9z6cKAR0oEozhjkYPaQRpnQQG/fLQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type:content-transfer-encoding; b=OJK1xxfQRJ+VDe5fWnN79UOkpOuVLf1QocsycAZk0vad8VdBMhAb+MI1dlbiFAVwEv 0fDg3NGB3+8iCuo6dZukIY3VcjI2O4sT0QWwEjO4NBpJA8ufDk0RWfJdfQIelYrXx2nL FCTDGGhT80LcfBCsCkRzWjOK1qNVNUIYKQYjE= Received: by 10.216.87.5 with SMTP id x5mr746888wee.90.1275546102191; Wed, 02 Jun 2010 23:21:42 -0700 (PDT) MIME-Version: 1.0 Received: by 10.216.17.197 with HTTP; Wed, 2 Jun 2010 23:21:22 -0700 (PDT) In-Reply-To: References: From: Jonathan Ellis Date: Wed, 2 Jun 2010 23:21:22 -0700 Message-ID: Subject: Re: Handling disk-full scenarios To: user@cassandra.apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable this is why JBOD configuration is contraindicated for cassandra. http://wiki.apache.org/cassandra/CassandraHardware On Tue, Jun 1, 2010 at 1:08 PM, Ian Soboroff wrote: > My nodes have 5 disks and are using them separately as data disks.=A0 The > usage on the disks is not uniform, and one is nearly full.=A0 Is there so= me > way to manually balance the files across the disks?=A0 Pretty much anythi= ng > done via nodetool incurs an anticompaction with obviously fails.=A0 syste= m/ is > not the problem, it's in my data's keyspace. > > Ian > > --=20 Jonathan Ellis Project Chair, Apache Cassandra co-founder of Riptano, the source for professional Cassandra support http://riptano.com