[ https://issues.apache.org/jira/browse/HBASE-27365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17612373#comment-17612373 ]
Hudson commented on HBASE-27365: -------------------------------- Results for branch master [build #692 on builds.a.o|https://ci-hbase.apache.org/job/HBase%20Nightly/job/master/692/]: (x) *{color:red}-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/master/692/General_20Nightly_20Build_20Report/] (x) {color:red}-1 jdk8 hadoop3 checks{color} -- For more information [see jdk8 (hadoop3) report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/master/692/JDK8_20Nightly_20Build_20Report_20_28Hadoop3_29/] (x) {color:red}-1 jdk11 hadoop3 checks{color} -- For more information [see jdk11 report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/master/692/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} > Minimise block addition failures due to no space in bucket cache writers > queue by introducing wait time > ------------------------------------------------------------------------------------------------------- > > Key: HBASE-27365 > URL: https://issues.apache.org/jira/browse/HBASE-27365 > Project: HBase > Issue Type: Improvement > Components: BucketCache > Reporter: Rajeshbabu Chintaguntla > Assignee: Rajeshbabu Chintaguntla > Priority: Major > > Currently in bucket cache asynchronous caching mechanism introduced where > initially the blocks to be cached will be added to queue and writer threads > consume the blocks from the queue and write to bucket cache. In case if block > writing to bucket cache is slow then there is a chance that queue of writer > threads become full and following block additions will be failed. In case of > slower storages like s3 might introduce latencies even if we enable bigger > sizes of bucket cache using ephemeral storages. So we can allow configurable > wait time while adding blocks to queue so that chances of queue free up is > possible during the wait time and block addition failures can be minimised. > To avoid the performance impact of wait time in regular read paths we can use > the wait time mainly during background operations like compactions, flushes > or prefetches etc. -- This message was sent by Atlassian Jira (v8.20.10#820010)