Details
Description
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 .
Attachments
Attachments
Issue Links
- breaks
-
HBASE-22617 Recovered WAL directories not getting cleaned up
- Closed
- is related to
-
HBASE-17437 Support specifying a WAL directory outside of the root directory
- Closed
- relates to
-
HBASE-20723 Custom hbase.wal.dir results in data loss because we write recovered edits into a different place than where the recovering region server looks for them
- Closed
-
HBASE-21544 Backport HBASE-20734 Colocate recovered edits directory with hbase.wal.dir
- Closed
-
HBASE-22200 WALSplitter.hasRecoveredEdits should use same FS instance from WAL region dir
- Closed
- links to