You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Misty Stanley-Jones (JIRA)" <ji...@apache.org> on 2015/08/10 01:25:45 UTC
[jira] [Commented] (HBASE-13129) Add troubleshooting hints around
WAL retention from replication
[ https://issues.apache.org/jira/browse/HBASE-13129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14679400#comment-14679400 ]
Misty Stanley-Jones commented on HBASE-13129:
---------------------------------------------
Is this addressed by HBASE-14071?
> Add troubleshooting hints around WAL retention from replication
> ---------------------------------------------------------------
>
> Key: HBASE-13129
> URL: https://issues.apache.org/jira/browse/HBASE-13129
> Project: HBase
> Issue Type: Improvement
> Components: documentation, Replication
> Reporter: Sean Busbey
> Labels: operations, supportability
>
> There's been some confusion on the mailing list about when WALs get retained / cleaned up once replication is on at all in a cluster. (ref [this thread|http://mail-archives.apache.org/mod_mbox/hbase-user/201502.mbox/%3CCAMUu0w9aOVBo7kGULiM9tXrULirqs9fm-3ra3pQccYpW_17uOw@mail.gmail.com%3E])
> We should add a NOTE in the replication section that wals are saved across enable/disable so long as there are peers. There looks like there might also be some confusing language around replication being enabled in the configs vs the enable/disable suspension mechanism.
> We should also add a troubleshooting item specific for "my HDFS space keeps growing and it's all in oldWALs."
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)