You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "leizhang (JIRA)" <ji...@apache.org> on 2019/06/24 06:10:00 UTC
[jira] [Updated] (HBASE-22620) When a cluster open
replication,regionserver will not clean up the walLog references on zk due
to no wal entry need to replicate
[ https://issues.apache.org/jira/browse/HBASE-22620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
leizhang updated HBASE-22620:
-----------------------------
Summary: When a cluster open replication,regionserver will not clean up the walLog references on zk due to no wal entry need to replicate (was: When a cluster open replication,regionserver will not clean up the walLog references on zk due to no data to replicate)
> When a cluster open replication,regionserver will not clean up the walLog references on zk due to no wal entry need to replicate
> --------------------------------------------------------------------------------------------------------------------------------
>
> Key: HBASE-22620
> URL: https://issues.apache.org/jira/browse/HBASE-22620
> Project: HBase
> Issue Type: Improvement
> Components: Replication
> Affects Versions: 2.0.3, 1.4.9
> Reporter: leizhang
> Priority: Major
>
> When I open the replication feature on my hbase cluster (20 regionserver nodes), for example, I create a table with 3 regions, which opened on 3 regionservers of 20. Due to no data to replicate ,the left 17 nodes accumulate lots of wal references on the zk node "/hbase/replication/rs/\{resionserver}/\{peerId}/" and will not be cleaned up, which cause lots of wal file on hdfs will not be cleaned up either. When I check my test cluster after about four months, it accumulates about 5w wal files in the oldWal directory on hdfs. The source code shows that only there are data to be replicated, and after some data is replicated in the source endpoint, then it will executed the useless wal file check, and clean their references on zk, and the hdfs useless wal files will be cleaned up normally. So I think do we need other method to trigger the useless wal cleaning job in a replication cluster? May be in the replication progress report schedule task (just like ReplicationStatisticsTask.class)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)