Return-Path: X-Original-To: apmail-hadoop-common-user-archive@www.apache.org Delivered-To: apmail-hadoop-common-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 89115E38B for ; Fri, 23 Nov 2012 07:43:37 +0000 (UTC) Received: (qmail 47189 invoked by uid 500); 23 Nov 2012 07:43:32 -0000 Delivered-To: apmail-hadoop-common-user-archive@hadoop.apache.org Received: (qmail 47068 invoked by uid 500); 23 Nov 2012 07:43:31 -0000 Mailing-List: contact user-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@hadoop.apache.org Delivered-To: mailing list user@hadoop.apache.org Received: (qmail 47041 invoked by uid 99); 23 Nov 2012 07:43:30 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 23 Nov 2012 07:43:30 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of harsh@cloudera.com designates 209.85.223.176 as permitted sender) Received: from [209.85.223.176] (HELO mail-ie0-f176.google.com) (209.85.223.176) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 23 Nov 2012 07:43:24 +0000 Received: by mail-ie0-f176.google.com with SMTP id 13so7584587iea.35 for ; Thu, 22 Nov 2012 23:43:03 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type:x-gm-message-state; bh=FZV3E/Op0olcyh9Zv8RVSh+jx3Fl80MjzHdq+XaAR9E=; b=YNUPVTy1OI2W1jRGpX3FoUOqENV7HVXOGwi7Ntb0m7E01FKrF/SWj2fEXRaP6ZYSy6 PaiAbZ2BzflOQbtb7JYi4yk8Rxgl8pgUIFzBlCDIdsGp6YD4clk6NlRNIHQkcty6kbGX /B2GZw58lAbHj3lmPzvC8R92kfSBkISA2BUt7hIa+53mTyuqf13y2gRByuDUu1474bMq mfh/ajiElMDZqaMiv4hYNkGwODcfXdQdBWU00LK3ErqquMyY5OcTmGKk6AfCENoq6WPO HMwJi1viokgNqDTIInuWgYVbaMgQjA8mw12kHdsmHLwiTveLFgKQb5Mc4TffjWJdVegh GwmQ== Received: by 10.50.195.130 with SMTP id ie2mr2809818igc.40.1353656583826; Thu, 22 Nov 2012 23:43:03 -0800 (PST) MIME-Version: 1.0 Received: by 10.64.6.129 with HTTP; Thu, 22 Nov 2012 23:42:43 -0800 (PST) In-Reply-To: References: From: Harsh J Date: Fri, 23 Nov 2012 13:12:43 +0530 Message-ID: Subject: Re: Log files occupy lot of Disk size To: "" Content-Type: text/plain; charset=ISO-8859-1 X-Gm-Message-State: ALoCoQmlBm5bcL13Qz/TRoiIAJS2zQg83EZkQgO4K+NK4OLvLkfQBA4+AEhiN/s1w70t97U88NnL X-Virus-Checked: Checked by ClamAV on apache.org Lower your log levels if you do not need all that verbosity. You can control log retention, max sizes to keep, max number of files to keep, and logging levels, etc. via each components' log4j.properties file. On Fri, Nov 23, 2012 at 12:42 PM, iwannaplay games wrote: > If i delete the log file without stopping the cluster won't it > terminate the session. > > > > On 11/23/12, Mohammad Tariq wrote: >> Hi there, >> >> You can write a small job or some script which periodically checks for >> the log growth and performs the delete after certain threshold. >> >> Regards, >> Mohammad Tariq >> >> >> >> On Fri, Nov 23, 2012 at 12:28 PM, iwannaplay games < >> funnlearnforkids@gmail.com> wrote: >> >>> Hi, >>> >>> Everytime i query hbase or hive ,there is a significant growth in my >>> log files and it consumes lot of space from my hard disk....(Approx 40 >>> gb) >>> So i stop the cluster ,delete all the logs and free the space and then >>> again start the cluster to start my work. >>> >>> Is there any other solution coz i cannot restart the cluster everyday. >>> >> -- Harsh J