You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Sean Busbey (JIRA)" <ji...@apache.org> on 2015/11/20 08:03:11 UTC

[jira] [Updated] (HBASE-14287) Bootstrapping a cluster leaves temporary WAL directory laying around

     [ https://issues.apache.org/jira/browse/HBASE-14287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sean Busbey updated HBASE-14287:
--------------------------------
    Assignee: Ted Yu

> 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
>            Assignee: Ted Yu
>            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)