You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hbase.apache.org by "Enis Soztutar (JIRA)" <ji...@apache.org> on 2014/08/30 00:33:53 UTC

[jira] [Commented] (HBASE-11863) WAL files are not archived and stays in the WAL directory after splitting

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

Enis Soztutar commented on HBASE-11863:
---------------------------------------

It seems that this has already been fixed by HBASE-11654 for 0.98. I am now checking to see whether master and branch-1 has this issue. In any case, I have 2 more unit tests that we can commit as a part of this issue. 

> WAL files are not archived and stays in the WAL directory after splitting 
> --------------------------------------------------------------------------
>
>                 Key: HBASE-11863
>                 URL: https://issues.apache.org/jira/browse/HBASE-11863
>             Project: HBase
>          Issue Type: Bug
>            Reporter: Enis Soztutar
>            Assignee: Enis Soztutar
>             Fix For: 0.99.0, 2.0.0, 0.98.6
>
>
> In patch HBASE-11094, it seems that we changed the constructor we are using for SplitLogManager, which does not archive the log files after splitting is done to the archive folder. The log files stays in the splitting directory forever and re-split every time the master restarts. 
> It is surprising that our unit tests are passing (since 0.94.4) without any issues. Part of the reason is that the split is actually carried, but the WAL is not moved and thus the -splitting directory never gets deleted. 
> It seems critical to fix in 0.98.6, [~andrew.purtell@gmail.com] FYI. 



--
This message was sent by Atlassian JIRA
(v6.2#6252)