You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Reid Chan (JIRA)" <ji...@apache.org> on 2019/08/15 14:58:00 UTC
[jira] [Commented] (HBASE-22861) [WAL] Merged region should get its
WAL according to WALProvider.
[ https://issues.apache.org/jira/browse/HBASE-22861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16908151#comment-16908151 ]
Reid Chan commented on HBASE-22861:
-----------------------------------
It only affects branch-1.
Branch-2 and master work fine.
> [WAL] Merged region should get its WAL according to WALProvider.
> ----------------------------------------------------------------
>
> Key: HBASE-22861
> URL: https://issues.apache.org/jira/browse/HBASE-22861
> Project: HBase
> Issue Type: Bug
> Reporter: Reid Chan
> Priority: Major
>
> This one is similar to HBASE-22774.
> Merging regions works fine by default because all regions shared one wal. But if multiwal is enabled, merged region should get its wal according to strategy.
> {code:title=HRegion.java|borderStyle=solid}
> HRegion createMergedRegionFromMerges(final HRegionInfo mergedRegionInfo,
> final HRegion region_b) throws IOException {
> HRegion r = HRegion.newHRegion(this.fs.getTableDir(),
> this.getWAL(), // Here should use rsService.getWAL(mergedRegionInfo), then wal provider and strategy if there is will take effect.
> fs.getFileSystem(), this.getBaseConf(), mergedRegionInfo,
> this.getTableDesc(), this.rsServices);
> ...
> return r;
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)