You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "Huaxiang Sun (Jira)" <ji...@apache.org> on 2021/09/09 17:56:00 UTC

[jira] [Resolved] (HBASE-26255) Add an option to use region location from meta table in TableSnapshotInputFormat

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

Huaxiang Sun resolved HBASE-26255.
----------------------------------
    Fix Version/s: 2.4.7
                   2.3.7
                   3.0.0-alpha-2
       Resolution: Fixed

> Add an option to use region location from meta table in TableSnapshotInputFormat
> --------------------------------------------------------------------------------
>
>                 Key: HBASE-26255
>                 URL: https://issues.apache.org/jira/browse/HBASE-26255
>             Project: HBase
>          Issue Type: Improvement
>          Components: mapreduce
>    Affects Versions: 2.3.6
>            Reporter: Huaxiang Sun
>            Assignee: Huaxiang Sun
>            Priority: Major
>             Fix For: 3.0.0-alpha-2, 2.3.7, 2.4.7
>
>
> TableSnapshotInputFormat currently calculates block locality of a region to decide the best location to run the task. While this works for a small scale table snapshot, we found that for a table snapshot with many regions, the locality calculation takes too much time. 
> In the case of a table with high locality, we can use region location from meta table to decide a snapshot region's location. Add an option to support it.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)