[
https://issues.apache.org/jira/browse/HBASE-14287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14742556#comment-14742556
]
Hudson commented on HBASE-14287:
--------------------------------
FAILURE: Integrated in HBase-1.3-IT #150 (See
[https://builds.apache.org/job/HBase-1.3-IT/150/])
HBASE-14287 Bootstrapping a cluster leaves temporary WAL directory laying
around (tedyu: rev d98ea9bb4e43f587f7e273555ae772c73fa38621)
*
hbase-server/src/main/java/org/apache/hadoop/hbase/master/MasterFileSystem.java
> Bootstrapping a cluster leaves temporary WAL directory laying around
> --------------------------------------------------------------------
>
> Key: HBASE-14287
> URL: https://issues.apache.org/jira/browse/HBASE-14287
> Project: HBase
> Issue Type: Bug
> Components: master, regionserver
> Affects Versions: 1.0.2, 1.1.1
> Reporter: Lars George
> Priority: Minor
> Fix For: 1.2.0, 1.3.0, 1.0.3, 1.1.3
>
> Attachments: 14287-branch-1.txt
>
>
> When a new cluster is started, it creates a temporary WAL as {{hbase:meta}}
> is created during bootstrapping the system. Then this log is closed before
> properly opened on a region server. The temp WAL file is scheduled for
> removal, moved to oldWALs and eventually claimed. Issue is that the WAL
> directory with the temp region is not removed. For example:
> {noformat}
> drwxr-xr-x - hadoop hadoop 0 2015-05-28 10:21
> /hbase/WALs/hregion-65589555
> {noformat}
> The directory is empty and does not harm, but on the other hand it is not
> needed anymore and should be removed. Cosmetic and good housekeeping.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
