Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Tue, 28 Jun 2016 14:44:57 +0000 (UTC)
From: "Ted Yu (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12984318.1467109167000.7468.1467125097075@Atlassian.JIRA>
In-Reply-To: <JIRA.12984318.1467109167000@Atlassian.JIRA>
References: <JIRA.12984318.1467109167000@Atlassian.JIRA> <JIRA.12984318.1467109167957@arcas>
Subject: [jira] [Commented] (HBASE-16135) PeerClusterZnode under rs of
 removed peer may never be deleted
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Tue, 28 Jun 2016 14:44:58 -0000


    [ https://issues.apache.org/jira/browse/HBASE-16135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15353109#comment-15353109 ] 

Ted Yu commented on HBASE-16135:
--------------------------------

replicationQueues.getAllQueues() is used in test.
How about exposing replicationQueues.getAllQueues() through a method instead of making replicationQueues public ?

> PeerClusterZnode under rs of removed peer may never be deleted
> --------------------------------------------------------------
>
>                 Key: HBASE-16135
>                 URL: https://issues.apache.org/jira/browse/HBASE-16135
>             Project: HBase
>          Issue Type: Bug
>          Components: Replication
>    Affects Versions: 2.0.0
>            Reporter: Duo Zhang
>            Assignee: Duo Zhang
>         Attachments: HBASE-16135.patch
>
>
> One of our cluster run out of space recently, and we found that the .oldlogs directory had almost the same size as the data directory.
> Finally we found the problem is that, we removed a peer abort 3 months ago, but there are still some replication queue znode under some rs nodes. This prevents the deletion of .oldlogs.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)