[ 
https://issues.apache.org/jira/browse/HBASE-28176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17789553#comment-17789553
 ] 

Hudson commented on HBASE-28176:
--------------------------------

Results for branch branch-3
        [build #91 on 
builds.a.o|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-3/91/]: 
(/) *{color:green}+1 overall{color}*
----
details (if available):

(/) {color:green}+1 general checks{color}
-- For more information [see general 
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-3/91/General_20Nightly_20Build_20Report/]




(/) {color:green}+1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3) 
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-3/91/JDK8_20Nightly_20Build_20Report_20_28Hadoop3_29/]


(/) {color:green}+1 jdk11 hadoop3 checks{color}
-- For more information [see jdk11 
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-3/91/JDK11_20Nightly_20Build_20Report_20_28Hadoop3_29/]


(/) {color:green}+1 source release artifact{color}
-- See build output for details.


(/) {color:green}+1 client integration test{color}


> PrefetchExecutor should stop once cache reaches capacity
> --------------------------------------------------------
>
>                 Key: HBASE-28176
>                 URL: https://issues.apache.org/jira/browse/HBASE-28176
>             Project: HBase
>          Issue Type: Improvement
>    Affects Versions: 2.6.0, 3.0.0-alpha-4, 4.0.0-alpha-1
>            Reporter: Wellington Chevreuil
>            Assignee: Wellington Chevreuil
>            Priority: Major
>             Fix For: 2.6.0, 3.0.0-beta-1, 4.0.0-alpha-1
>
>
> The prefetch executor runs a full scan on regions in the background once 
> regions are opened, if the "hbase.rs.prefetchblocksonopen" property is set to 
> true. However, if the store file size is much larger than the cache capacity, 
> we should interrupt the prefetch once it has reached the cache capacity, 
> otherwise it would just be triggering evictions of little value, since we 
> don't have any sense of block priority at that point. It's better to stop the 
> read, and let client reads cause the eviction of LFU blocks and cache the 
> most accessed blocks.



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

Reply via email to