[
https://issues.apache.org/jira/browse/HBASE-14287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14742411#comment-14742411
]
Lars George commented on HBASE-14287:
-------------------------------------
Indeed! HBASE-12204 misses the updated line from HBASE-11982 and reverts it
back. [~tedyu] mind to fix this with an addendum?
{noformat}
- setInfoFamilyCachingForMeta(false);
- HRegion meta = HRegion.createHRegion(metaHRI, rd, c,
- HTableDescriptor.META_TABLEDESC, null, true, true);
- setInfoFamilyCachingForMeta(true);
+ HTableDescriptor metaDescriptor = new
FSTableDescriptors(c).get(TableName.META_TABLE_NAME);
+ setInfoFamilyCachingForMeta(metaDescriptor, false);
+ HRegion meta = HRegion.createHRegion(metaHRI, rd, c, metaDescriptor);
+ setInfoFamilyCachingForMeta(metaDescriptor, true)
{noformat}
> 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
>
> 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)
