[
https://issues.apache.org/jira/browse/HBASE-20734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16592056#comment-16592056
]
Zach York commented on HBASE-20734:
-----------------------------------
I haven't updated the branch-1 patch for that yet, I was waiting on some
feedback on the master approach to avoid having to maintain two patches for all
updates. I'll update the branch-1 patch when the master patch is agreed upon.
If you are coming from a world where HBASE-20723 isn't applied and using a
custom wal.dir, then yeah, it isn't really necessary, but since we have applied
HBASE-20723 to a couple releases, we need to do the same thing in branch-1. For
your testing though, the current branch-1 patch might be sufficient (if you
have a custom wal.dir with no data that needs to be recovered yet)
> 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
> Assignee: Zach York
> Priority: Major
> Fix For: 3.0.0
>
> Attachments: HBASE-20734.branch-1.001.patch,
> HBASE-20734.master.001.patch, HBASE-20734.master.002.patch,
> HBASE-20734.master.003.patch, HBASE-20734.master.004.patch
>
>
> 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)
