You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "Duo Zhang (Jira)" <ji...@apache.org> on 2022/11/05 15:26:00 UTC

[jira] [Resolved] (HBASE-27414) Search order for locations in HFileLink

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

Duo Zhang resolved HBASE-27414.
-------------------------------
    Fix Version/s: 2.6.0
                   3.0.0-alpha-4
                   2.5.2
                   2.4.16
     Hadoop Flags: Reviewed
         Assignee: ruanhui
       Resolution: Fixed

Pushed to branch-2.4=.

Thanks [~frostruan] for contributing and thanks [~stack] for confirming!

> Search order for locations in  HFileLink
> ----------------------------------------
>
>                 Key: HBASE-27414
>                 URL: https://issues.apache.org/jira/browse/HBASE-27414
>             Project: HBase
>          Issue Type: Improvement
>          Components: Performance
>            Reporter: Huaxiang Sun
>            Assignee: ruanhui
>            Priority: Minor
>             Fix For: 2.6.0, 3.0.0-alpha-4, 2.5.2, 2.4.16
>
>
> Found that search order for locations is following the order of these locations added to HFileLink object. 
>  
> setLocations(originPath, tempPath, mobPath, archivePath);
> archivePath is the last one to be searched. For most cases, hfile exists in archivePath, so we can move archivePath to the first parameter to avoid unnecessary NN query.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)