You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Ted Yu (JIRA)" <ji...@apache.org> on 2018/06/21 16:08:00 UTC

[jira] [Comment Edited] (HBASE-20734) Colocate recovered edits directory with hbase.wal.dir

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

Ted Yu edited comment on HBASE-20734 at 6/21/18 4:07 PM:
---------------------------------------------------------

In WALSplitter#finishSplitLogFile :
{code}
    Path rootdir = FSUtils.getWALRootDir(conf);
{code}
Probably renaming rootdir as walRootDir would make the code clearer (since rootdir means different directory w.r.t. {{FSUtils.getRootDir}})


was (Author: yuzhihong@gmail.com):
In WALSplitter#finishSplitLogFile :

    Path rootdir = FSUtils.getWALRootDir(conf);

Probably renaming rootdir as walRootDir would make the code clearer (since rootdir means different directory w.r.t. {{FSUtils.getWALRootDir}})

> Colocate recovered edits directory with hbase.wal.dir
> -----------------------------------------------------
>
>                 Key: HBASE-20734
>                 URL: https://issues.apache.org/jira/browse/HBASE-20734
>             Project: HBase
>          Issue Type: Improvement
>          Components: MTTR, Recovery, wal
>            Reporter: Ted Yu
>            Priority: Major
>             Fix For: 3.0.0
>
>
> During investigation of HBASE-20723, I realized that we wouldn't get the best performance when hbase.wal.dir is configured to be on different (fast) media than hbase rootdir w.r.t. recovered edits since recovered edits directory is currently under rootdir.
> Such setup may not result in fast recovery when there is region server failover.
> This issue is to find proper (hopefully backward compatible) way in colocating recovered edits directory with hbase.wal.dir .



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)