Return-Path: X-Original-To: apmail-hbase-issues-archive@www.apache.org Delivered-To: apmail-hbase-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 1B64118D19 for ; Wed, 28 Oct 2015 21:43:28 +0000 (UTC) Received: (qmail 58849 invoked by uid 500); 28 Oct 2015 21:43:27 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 58791 invoked by uid 500); 28 Oct 2015 21:43:27 -0000 Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list issues@hbase.apache.org Received: (qmail 58777 invoked by uid 99); 28 Oct 2015 21:43:27 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 28 Oct 2015 21:43:27 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id B3C2E2C1F58 for ; Wed, 28 Oct 2015 21:43:27 +0000 (UTC) Date: Wed, 28 Oct 2015 21:43:27 +0000 (UTC) From: "Elliott Clark (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HBASE-14712) MasterProcWALs never clean up MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HBASE-14712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14979300#comment-14979300 ] Elliott Clark commented on HBASE-14712: --------------------------------------- [~mbertozzi] Every cluster we have with 1.2 running has logs dating back multiple days and nothing currently running on them. > MasterProcWALs never clean up > ----------------------------- > > Key: HBASE-14712 > URL: https://issues.apache.org/jira/browse/HBASE-14712 > Project: HBase > Issue Type: Bug > Reporter: Elliott Clark > Priority: Blocker > > MasterProcWALs directory grows pretty much un-bounded. Because of that when master failover happens the NN is flooded with connections and everything grinds to a halt. -- This message was sent by Atlassian JIRA (v6.3.4#6332)