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 60BA99C29 for ; Mon, 8 Dec 2014 21:51:04 +0000 (UTC) Received: (qmail 72109 invoked by uid 500); 8 Dec 2014 21:51:02 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 72040 invoked by uid 500); 8 Dec 2014 21:51:02 -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 72022 invoked by uid 99); 8 Dec 2014 21:51:01 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 08 Dec 2014 21:51:01 +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 (athena.apache.org: domain of yuzhihong@gmail.com designates 209.85.213.49 as permitted sender) Received: from [209.85.213.49] (HELO mail-yh0-f49.google.com) (209.85.213.49) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 08 Dec 2014 21:50:57 +0000 Received: by mail-yh0-f49.google.com with SMTP id f10so2691743yha.8 for ; Mon, 08 Dec 2014 13:49:51 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=K0JxhHFFfqvNe/ZiHV5eigSZwgBFiYO1qFpDB4Lolpc=; b=lPpFEGs84AlKquBPHUKt7UdyWKatzoynRtAJfyBtxTQ3bvr2POk3dAegWoyhf1hl3j ye5Vm2ICZIDH35sPywcdlWpWtK11gu9EhhniKfD8x4mPJeBS5dfBxvcsUt324mZih1oV Vs3rMmuKsCJurvLfPs04+fSHrKx/urTBvXMM5vqskHNGAf6WDnepepdWCdUKrxfU8gMz Nls9npV4tl88A70pu4ECOEAldQH2vUqo814lNKSPGmosvh3fMtl79HgLLO7H0rHG9O+/ 58Z5FV8kw+iNwyhQeLVcVTqoK8NrpOVWPAbpEQYsnis3GM8Xb9w7qleVGQx6/CaPQ6Gk IHoQ== MIME-Version: 1.0 X-Received: by 10.170.186.66 with SMTP id c63mr36782721yke.46.1418075391522; Mon, 08 Dec 2014 13:49:51 -0800 (PST) Received: by 10.170.145.67 with HTTP; Mon, 8 Dec 2014 13:49:51 -0800 (PST) In-Reply-To: References: Date: Mon, 8 Dec 2014 13:49:51 -0800 Message-ID: Subject: Re: Can I delete oldLogs from Hbase? From: Ted Yu To: "user@hbase.apache.org" Content-Type: multipart/alternative; boundary=001a11394150fa007f0509bb6768 X-Virus-Checked: Checked by ClamAV on apache.org --001a11394150fa007f0509bb6768 Content-Type: text/plain; charset=UTF-8 0.94.6 is pretty old. Looking at change history of ReplicationLogCleaner.java, you would see changes that went in after 0.94.6 e.g. HBASE-9377: Backport HBASE- 9208 - ReplicationLogCleaner slow at large scale (Dave Latham) Can you upgrade to newer release ? On Mon, Dec 8, 2014 at 1:32 PM, Yaniv Yancovich wrote: > Hi, > I am using hbase 0.94.6 (CDH 4.5). > I saw that my oldLogs folder keeps growing to 4.4T. This stopped at early > October, but still the files doesn't being cleaned. > Can I delete them? Why do i need them on first place? > > I see in master log the following NPE: > 2014-07-17 08:15:05,862 ERROR > org.apache.hadoop.hbase.master.cleaner.LogCleaner: Caught exception > java.lang.NullPointerException > at > org.apache.hadoop.hbase.replication.ReplicationZookeeper.get > ListHLogsForPeerForRS(ReplicationZookeeper.java:625) > at > > org.apache.hadoop.hbase.replication.master.ReplicationLogCleaner.loadHLogsFromQueues(ReplicationLogCleaner.java:110) > at > org.apache.hadoop.hbase.replication.master.ReplicationLogCleaner.get > DeletableFiles(ReplicationLogCleaner.java:76) > at > > org.apache.hadoop.hbase.master.cleaner.CleanerChore.checkAndDeleteFiles(CleanerChore.java:234) > at > > org.apache.hadoop.hbase.master.cleaner.CleanerChore.checkAndDeleteEntries(CleanerChore.java:158) > at > > org.apache.hadoop.hbase.master.cleaner.CleanerChore.chore(CleanerChore.java:125) > at org.apache.hadoop.hbase.Chore.run(Chore.java:67) > at java.lang.Thread.run(Thread.java:744) > > I checked for old hbase-defaults.xml in master conf and didn't find such. > > Any ideas? > --001a11394150fa007f0509bb6768--