[
https://issues.apache.org/jira/browse/HBASE-21509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16697748#comment-16697748
]
Allan Yang commented on HBASE-21509:
------------------------------------
{quote}
but meta log is not empty
{quote}
Yes, it is possible, the reason is that the meta region was once on this
server, it was moved to another RS, but somehow, the log was not cleared after
this server closed the meta region.
Since this server don't have the meta region when it crashed(restarted by you),
the meta log won't be split, thus this directory will remain there forever.
But don't panic, it won't cause meta table lose any data.
> /hbase/WALs directory has large number of hlogs, which cannot be deleted
> correctly
> ----------------------------------------------------------------------------------
>
> Key: HBASE-21509
> URL: https://issues.apache.org/jira/browse/HBASE-21509
> Project: HBase
> Issue Type: Bug
> Affects Versions: 1.3.1
> Reporter: Bo Cui
> Priority: Minor
>
> When HMaster is initializing, if getMetaRegionLocation() returns null value,
> then some wal(including metaWAL) cannot be deleted.
> for example
> before restarts
> /hbase/WALs/10-10-10-129,21302,1543048601526/10-10-10-129%2C21302%2C1543048601526.meta.1543048613941.meta
> after restarts
> /hbase/WALs/10-10-10-129,21302,1543048601526-splitting/10-10-10-129%2C21302%2C1543048601526.meta.1543048613941.meta
> /hbase/WALs/10-10-10-29,21302,1543048867527/10-10-10-29%2C21302%2C1543048867527.meta.1543048907265.meta
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
