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

Andrew Purtell commented on HBASE-22617:
----------------------------------------

After the fix is ready we should also have a unit test that confirms that no 
files are written outside of where we expect, so we can catch this kind of 
error in the future. Could be done as part of this work or as a follow up PR 
and JIRA, but we should have that additional test coverage in place going 
forward.

> 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, 1.5.0, 2.3.0, 2.0.6, 2.2.1, 2.1.6, 1.4.11
>
>
> 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)

Reply via email to