Return-Path: X-Original-To: apmail-hbase-dev-archive@www.apache.org Delivered-To: apmail-hbase-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 38EAF108F1 for ; Tue, 18 Mar 2014 12:29:36 +0000 (UTC) Received: (qmail 9083 invoked by uid 500); 18 Mar 2014 12:29:32 -0000 Delivered-To: apmail-hbase-dev-archive@hbase.apache.org Received: (qmail 8895 invoked by uid 500); 18 Mar 2014 12:29:31 -0000 Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@hbase.apache.org Delivered-To: mailing list dev@hbase.apache.org Received: (qmail 8883 invoked by uid 99); 18 Mar 2014 12:29:30 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 18 Mar 2014 12:29:30 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of haosdent@gmail.com designates 209.85.216.44 as permitted sender) Received: from [209.85.216.44] (HELO mail-qa0-f44.google.com) (209.85.216.44) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 18 Mar 2014 12:29:24 +0000 Received: by mail-qa0-f44.google.com with SMTP id f11so6827668qae.31 for ; Tue, 18 Mar 2014 05:29:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=z+1Obna5Jy3RclJNJgzvKJYbkj6NaB7wIRCGeVaHV0A=; b=ifzQdnxcEbltZDgvR2dEv1TKvioBOTui8xjKqn3vjKWyMBnbbugeEgttx5N0L5tSqA 1lsfsXAYAvhrCQ4fBPSyHs3hVDxoQX9KkQQNzCNbGj+j7mQEfRG0pzuNaoBXKMrpk8ya /iAFN/ihu/R5ZkldHiWzp6qhpvajnZ7MQxR/6biOvizbKdrdeKesWuaE6GQ+rBzsgwj3 8N1I8aU6RWmKca5Dgkwu0z9FvnGFH6V9EGhnnphxoekJF3vvoTJrrw/WLXS1sJCiCy7p ALcF4KiW9lrhXeBFblGd1Hi78uaHGd0Jvl0N09Av2X/bdPcxentAMs64GmXe07asjS8i 5iyQ== MIME-Version: 1.0 X-Received: by 10.224.96.138 with SMTP id h10mr34936197qan.46.1395145742864; Tue, 18 Mar 2014 05:29:02 -0700 (PDT) Received: by 10.140.50.129 with HTTP; Tue, 18 Mar 2014 05:29:02 -0700 (PDT) Date: Tue, 18 Mar 2014 20:29:02 +0800 Message-ID: Subject: Is there a better way to handle too much log From: haosdent To: hbase-dev Content-Type: multipart/alternative; boundary=001a11c3f50669e08204f4e0ae82 X-Virus-Checked: Checked by ClamAV on apache.org --001a11c3f50669e08204f4e0ae82 Content-Type: text/plain; charset=ISO-8859-1 Sometimes the call of Log.xxx couldn't return if the disk partition of Log path is full. And HBase would hang because of this. So I think if there is a better way to handle too much log. For example, through a configuration item in hbase-site.xml, we could delete the old logs periodically or delete old logs when this disk didn't have enough space. I think HBase hang when disk space isn't enough is unacceptable. Looking forward your ideas. Thanks in advance. -- Best Regards, Haosdent Huang --001a11c3f50669e08204f4e0ae82--