[
https://issues.apache.org/jira/browse/HBASE-14247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14708910#comment-14708910
]
Liu Shaohui commented on HBASE-14247:
-------------------------------------
[~davelatham]
{quote}
One concern with this change is that the OldLogCleaner as it is implemented
will now have to run through the cleaner checks for every regionserver's
subdirectory instead of doing them all in one batch. It will likely make the
cleaner chore much slower and may not be able to keep up for large clusters.
{quote}
I don't think this will be problem. Currenly the HFileCleaner have to run
through the cleaner checks for every store's subdirectory of every region of
every table and we didn't see the problem of efficiency. So I won't need to
worry about the OldLogCleaner in new layout of old layout.
What's more, we can turn up the cleaner period by config
hbase.master.cleaner.interval.
> Separate the old WALs into different regionserver directories
> -------------------------------------------------------------
>
> Key: HBASE-14247
> URL: https://issues.apache.org/jira/browse/HBASE-14247
> Project: HBase
> Issue Type: Improvement
> Reporter: Liu Shaohui
> Assignee: Liu Shaohui
> Priority: Minor
> Fix For: 2.0.0
>
> Attachments: HBASE-14247-v001.diff, HBASE-14247-v002.diff
>
>
> Currently all old WALs of regionservers are achieved into the single
> directory of oldWALs. In big clusters, because of long TTL of WAL or disabled
> replications, the number of files under oldWALs may reach the
> max-directory-items limit of HDFS, which will make the hbase cluster crashed.
> {quote}
> Caused by:
> org.apache.hadoop.ipc.RemoteException(org.apache.hadoop.hdfs.protocol.FSLimitException$MaxDirectoryItemsExceededException):
> The directory item limit of /hbase/lgprc-xiaomi/.oldlogs is exceeded:
> limit=1048576 items=1048576
> {quote}
> A simple solution is to separate the old WALs into different directories
> according to the server name of the WAL.
> Suggestions are welcomed~ Thanks
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
