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 DCAE7671E for ; Fri, 8 Jul 2011 03:29:27 +0000 (UTC) Received: (qmail 83730 invoked by uid 500); 8 Jul 2011 03:29:25 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 83410 invoked by uid 500); 8 Jul 2011 03:29:18 -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 83400 invoked by uid 99); 8 Jul 2011 03:29:17 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 08 Jul 2011 03:29:17 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [122.224.216.65] (HELO hzvscan2.utstar.com.cn) (122.224.216.65) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 08 Jul 2011 03:29:12 +0000 Received: from cnmail01.cn.utstarcom.com (cnmail01.cn.utstarcom.com [172.18.22.151]) by hzvscan2.utstar.com.cn (8.13.8/8.13.8) with SMTP id p683SgbB010755 for ; Fri, 8 Jul 2011 11:28:42 +0800 Received: from CNMAIL12.cn.utstarcom.com ([172.18.22.156]) by cnmail01.cn.utstarcom.com with Microsoft SMTPSVC(6.0.3790.3959); Fri, 8 Jul 2011 11:28:42 +0800 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="GB2312" Content-Transfer-Encoding: quoted-printable Subject: cassandra server disk full X-MimeOLE: Produced By Microsoft Exchange V6.5 Date: Fri, 8 Jul 2011 11:28:42 +0800 Message-ID: <7DA4B654C7FEB24C9998EE4867BEE93EBC7D84@CNMAIL12.cn.utstarcom.com> In-Reply-To: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: cassandra server disk full Thread-Index: Acw9G6xKHGc+r2yARaav1Gzrm8QcqQAAw80g References: <7DA4B654C7FEB24C9998EE4867BEE93EBC7D50@CNMAIL12.cn.utstarcom.com> From: "Donna Li" To: X-OriginalArrivalTime: 08 Jul 2011 03:28:42.0235 (UTC) FILETIME=[22B32CB0:01CC3D1F] Does CASSANDRA-809 resolved or any other path can resolve the problem? = Is there any way to avoid reboot the cassandra server? Thanks! Best Regards Donna li -----=D3=CA=BC=FE=D4=AD=BC=FE----- =B7=A2=BC=FE=C8=CB: Jonathan Ellis [mailto:jbellis@gmail.com]=20 =B7=A2=CB=CD=CA=B1=BC=E4: 2011=C4=EA7=D4=C28=C8=D5 11:03 =CA=D5=BC=FE=C8=CB: user@cassandra.apache.org =D6=F7=CC=E2: Re: cassandra server disk full Yeah, ideally it should probably die or drop into read-only mode if it runs out of space. (https://issues.apache.org/jira/browse/CASSANDRA-809) Unfortunately dealing with disk-full conditions tends to be a low priority for many people because it's relatively easy to avoid with decent monitoring, but if it's critical for you, we'd welcome the assistance. On Thu, Jul 7, 2011 at 8:34 PM, Donna Li wrote: > All: > > When one of the cassandra servers disk full, the cluster can not work > normally, even I make space. I must reboot the server that disk full, = the > cluster can work normally. > > > > Best Regards > > Donna li --=20 Jonathan Ellis Project Chair, Apache Cassandra co-founder of DataStax, the source for professional Cassandra support http://www.datastax.com