Return-Path: X-Original-To: apmail-hbase-user-archive@www.apache.org Delivered-To: apmail-hbase-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 E4EE910913 for ; Fri, 18 Oct 2013 00:58:33 +0000 (UTC) Received: (qmail 61571 invoked by uid 500); 18 Oct 2013 00:58:31 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 61521 invoked by uid 500); 18 Oct 2013 00:58:31 -0000 Mailing-List: contact user-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@hbase.apache.org Delivered-To: mailing list user@hbase.apache.org Received: (qmail 61513 invoked by uid 99); 18 Oct 2013 00:58:31 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 18 Oct 2013 00:58:31 +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 enis.soz@gmail.com designates 209.85.216.173 as permitted sender) Received: from [209.85.216.173] (HELO mail-qc0-f173.google.com) (209.85.216.173) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 18 Oct 2013 00:58:25 +0000 Received: by mail-qc0-f173.google.com with SMTP id l13so2136748qcy.32 for ; Thu, 17 Oct 2013 17:58:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=wr3QsCizxI3oa0/IP4phYeSFOdDO9Hao3yekBUkI4sg=; b=JsP3dspv1skpb9ge7hGdn+uT4HJ04bv/3cC0H4k0//WdaWu7f+s2xAm+7Jk7nP/jpi Nk1Ipi3Kh9CiL7spdpdFdulKhzg5FnIxgsQBSxkvYu6YZUS97RkBTyNSmt6N4KD6O1sz VxZ23FBbctLdWHjDM/eXGNuX8PcoAU9MMH5ZkHD4JaobYD2jBG1j7qGZp987gQRVihrJ esS50o6VOIz7vYcisSH1Pr6Iw8uJQmj5wutAcMVjidpQYHQF12OUmfH+rJDm0ZzcGRM/ R7Ogq1iYwJ3WlHi8b8olG3qK/FptFK+qo6XExvUu1oF5GFMllDr72mhpHPp1Uu4FcZOi 72GQ== X-Received: by 10.49.109.10 with SMTP id ho10mr383541qeb.84.1382057884870; Thu, 17 Oct 2013 17:58:04 -0700 (PDT) MIME-Version: 1.0 Received: by 10.49.4.101 with HTTP; Thu, 17 Oct 2013 17:57:44 -0700 (PDT) In-Reply-To: <422919DD6D695D439A6B31B21B6F8BDE2C208B48@szxeml558-mbx.china.huawei.com> References: <422919DD6D695D439A6B31B21B6F8BDE2C208B48@szxeml558-mbx.china.huawei.com> From: =?UTF-8?Q?Enis_S=C3=B6ztutar?= Date: Thu, 17 Oct 2013 17:57:44 -0700 Message-ID: Subject: Re: hbase log4j.properties can we change to DRFA to RFA. To: hbase-user Content-Type: multipart/alternative; boundary=047d7bdca48849726b04e8f96d26 X-Virus-Checked: Checked by ClamAV on apache.org --047d7bdca48849726b04e8f96d26 Content-Type: text/plain; charset=UTF-8 You can change the log4j configuration for your deployment as you see fit. DRFA is however a better default for the general case. You might also want to ensure that you are not running with DEBUG logging enabled in a production cluster. Enis On Mon, Oct 14, 2013 at 11:01 PM, sreenivasulu y wrote: > Hi, > > Can we change log4j.properties > DailyRollingFileAppender to RollingFileAppender > With some specific size of the log file. > > Because of, with in a day may be a log file size will become 10GB to 12GB > (In our cluster its happen), because of some failure in the hbase cluster. > In hdfs component and all log rolling is done with RFA only. > > Please provide your comments for changing log4j.properties file. > --047d7bdca48849726b04e8f96d26--