You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Andrew Purtell (JIRA)" <ji...@apache.org> on 2019/06/25 16:40:00 UTC
[jira] [Resolved] (HBASE-22617) Recovered WAL directories not
getting cleaned up
[ https://issues.apache.org/jira/browse/HBASE-22617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrew Purtell resolved HBASE-22617.
------------------------------------
Resolution: Fixed
Hadoop Flags: Reviewed
> Recovered WAL directories not getting cleaned up
> ------------------------------------------------
>
> Key: HBASE-22617
> URL: https://issues.apache.org/jira/browse/HBASE-22617
> Project: HBase
> Issue Type: Bug
> Components: wal
> Affects Versions: 1.5.0
> Reporter: Abhishek Singh Chouhan
> Assignee: Duo Zhang
> Priority: Blocker
> Fix For: 3.0.0, 2.3.0, 2.0.6, 2.2.1, 2.1.6
>
>
> While colocating the recovered edits directory with hbase.wal.dir, BASE_NAMESPACE_DIR got missed. This results in recovered edits being put in a separate directory rather than the default region directory even if the hbase.wal.dir is not overridden. Eg. if data is stored in /hbase/data/namespace/table1, recovered edits are put in /hbase/namespace/table1. This also messes up the regular cleaner chores which never operate on this new directory and these directories will never be deleted, even for split parents or dropped tables. We should change the default back to have the base namespace directory in path.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)