[
https://issues.apache.org/jira/browse/HBASE-16135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15361423#comment-15361423
]
Hudson commented on HBASE-16135:
--------------------------------
SUCCESS: Integrated in HBase-1.3-IT #742 (See
[https://builds.apache.org/job/HBase-1.3-IT/742/])
HBASE-16135 PeerClusterZnode under rs of removed peer may never be (zhangduo:
rev a9b7f3f0219556fa8023fe4684aef3724e624597)
*
hbase-client/src/main/java/org/apache/hadoop/hbase/replication/ReplicationQueuesZKImpl.java
*
hbase-server/src/main/java/org/apache/hadoop/hbase/replication/regionserver/ReplicationSourceManager.java
*
hbase-server/src/test/java/org/apache/hadoop/hbase/replication/regionserver/TestReplicationSourceManager.java
> 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, 1.3.0, 1.4.0, 1.1.5, 1.2.2, 0.98.20
> Reporter: Duo Zhang
> Assignee: Duo Zhang
> Fix For: 2.0.0, 1.3.0, 1.4.0, 1.1.6, 0.98.21, 1.2.3
>
> Attachments: HBASE-16135-0.98.patch, HBASE-16135-branch-1.1.patch,
> HBASE-16135-branch-1.2.patch, HBASE-16135-branch-1.patch,
> HBASE-16135-v1.patch, HBASE-16135-v2.patch, HBASE-16135-v3.patch,
> 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)
