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 1B776F392 for ; Sat, 30 Mar 2013 14:56:46 +0000 (UTC) Received: (qmail 30215 invoked by uid 500); 30 Mar 2013 14:56:44 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 30169 invoked by uid 500); 30 Mar 2013 14:56:44 -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 30071 invoked by uid 99); 30 Mar 2013 14:56:39 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 30 Mar 2013 14:56:39 +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 azuryyyu@gmail.com designates 209.85.210.175 as permitted sender) Received: from [209.85.210.175] (HELO mail-ia0-f175.google.com) (209.85.210.175) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 30 Mar 2013 14:56:34 +0000 Received: by mail-ia0-f175.google.com with SMTP id y26so1018494iab.34 for ; Sat, 30 Mar 2013 07:56:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:content-type; bh=I/0V7OuqvST1Cu3pxde89BadBWn9rK1Kg0Rhu7ibJKw=; b=cCjiGKBPZ1UW0R70qdiTYSVznvyWJ8XaOr/4jlzJLhJA9NG55bIvGU/MYB5l1c9/n6 QYmIwDbNlHK+D3y/Tot7x29fUjBzyOIUYgUIOaGgWrF2b5xRDc1igtEhUqr/4r7xRjZg rMHyguJUGIt0zOIdqsy1yw3092FeiU47bp5EmpVAuAnscxaWQ0+SuFjyqJNjFY1PiE9u M2MI+yidlnMaf3Bf7MMGaqitPwYxl6elTz35r97AgXSCv31uxRAHOt6SyBK3U7cD00Um s17FOoxjOyOM3mLv9ai2jCu0z9Kamu4rrNO9UpTcD8nKwuKOEDm5UsLwz0A0KQwr475K WYNg== MIME-Version: 1.0 X-Received: by 10.50.1.38 with SMTP id 6mr1056110igj.106.1364655373144; Sat, 30 Mar 2013 07:56:13 -0700 (PDT) Received: by 10.64.26.70 with HTTP; Sat, 30 Mar 2013 07:56:13 -0700 (PDT) Received: by 10.64.26.70 with HTTP; Sat, 30 Mar 2013 07:56:13 -0700 (PDT) In-Reply-To: References: Date: Sat, 30 Mar 2013 22:56:13 +0800 Message-ID: Subject: Re: how to reduce zookeeper.out From: Azuryy Yu To: user@hbase.apache.org Content-Type: multipart/alternative; boundary=e89a8f839fc3c1ede404d92596d1 X-Virus-Checked: Checked by ClamAV on apache.org --e89a8f839fc3c1ede404d92596d1 Content-Type: text/plain; charset=ISO-8859-1 I think your hbase cluster zk is managed by hbase. you didnt install zk separately. so you can find zk log under hbase log dir. On Mar 30, 2013 10:42 PM, "hua beatls" wrote: > Hi Kevin, > seems there is no rolling mechanizm for the zookeeper.out. > > > > > On Sat, Mar 30, 2013 at 10:31 PM, Kevin O'dell >wrote: > > > Hi Hua, > > > > I believe(don't quote me) that you can use the rolling file appender to > > set the files to a max size. I know HBase does this, but I am not sure > > about ZK. > > > > On Sat, Mar 30, 2013 at 10:22 AM, Jean-Marc Spaggiari < > > jean-marc@spaggiari.org> wrote: > > > > > Hi, > > > > > > If you are in production you should have more than 1 ZK server, right? > > > Like, 3 or more? > > > > > > Then you can just shut one down, the others mike elect a new leader. > > > Then you clear the zookeeper.out file, and start it back? > > > > > > JM > > > > > > 2013/3/30 hua beatls : > > > > Hi, > > > > zookeeper.out is too large, how to reduce this file? it is a > online > > > > system. > > > > > > > > Best R. > > > > > > > > beatls > > > > > > > > > > > -- > > Kevin O'Dell > > Customer Operations Engineer, Cloudera > > > --e89a8f839fc3c1ede404d92596d1--