hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Reid Chan (Jira)" <j...@apache.org>
Subject [jira] [Resolved] (HBASE-22861) [WAL] Merged region should get its WAL according to WALProvider.
Date Thu, 22 Aug 2019 03:28:00 GMT

     [ https://issues.apache.org/jira/browse/HBASE-22861?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Reid Chan resolved HBASE-22861.
-------------------------------
    Hadoop Flags: Reviewed
      Resolution: Fixed

QA and actual tests on production cluster are good.

> [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
>          Components: wal
>    Affects Versions: 1.4.10, 1.3.5
>            Reporter: Reid Chan
>            Assignee: Reid Chan
>            Priority: Major
>             Fix For: 1.5.0, 1.3.6, 1.4.11
>
>
> 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 wal grouping 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
(v8.3.2#803003)

Mime
View raw message