[
https://issues.apache.org/jira/browse/HBASE-27414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17628989#comment-17628989
]
Duo Zhang edited comment on HBASE-27414 at 11/4/22 1:49 PM:
------------------------------------------------------------
The order is changed in this commit
https://github.com/apache/hbase/commit/f70ed5ab6de7cc71592a1714c9a3cc03b115c7fd
The commit message said it is for HBASE-7583, but checking the uploaded patch
for HBASE-7583, we did not touch HFileLink...
was (Author: apache9):
The order is changed in this commit
https://github.com/apache/hbase/commit/f70ed5ab6de7cc71592a1714c9a3cc03b115c7fd
The commit message said it is for HBASE-7583, but checking the uploaded patch
for HBASE-7593, we did not touch HFileLink...
> 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
> Priority: Minor
>
> 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)
