[ https://issues.apache.org/jira/browse/HBASE-27078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17564440#comment-17564440 ]
Hudson commented on HBASE-27078: -------------------------------- Results for branch branch-2.5 [build #160 on builds.a.o|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.5/160/]: (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/branch-2.5/160/General_20Nightly_20Build_20Report/] (x) {color:red}-1 jdk8 hadoop2 checks{color} -- For more information [see jdk8 (hadoop2) report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.5/160/JDK8_20Nightly_20Build_20Report_20_28Hadoop2_29/] (x) {color:red}-1 jdk8 hadoop3 checks{color} -- For more information [see jdk8 (hadoop3) report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.5/160/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/branch-2.5/160/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} > Allow configuring a separate timeout for meta scans > --------------------------------------------------- > > Key: HBASE-27078 > URL: https://issues.apache.org/jira/browse/HBASE-27078 > Project: HBase > Issue Type: Improvement > Reporter: Bryan Beaudreault > Assignee: Bryan Beaudreault > Priority: Major > Labels: patch-available > Fix For: 2.5.0, 3.0.0-alpha-4 > > > There is a {{hbase.client.meta.operation.timeout}} but it does not apply to > meta scans, which are the primary use-case for clients (i.e. through > RegionLocator). > Many user-facing clients may want to have low rpc and scan timeouts. However, > in periods of meta hotspotting, those timeouts can be way too low for the > meta scans. The problem with low timeouts for meta scans is that without a > populated MetaCache, user requests cannot succeed. In fact, user requests > will continually try to re-scan meta until the MetaCache is populated. So > having a lower rpc timeout will cause a situation where meta scans cannot > succeed, and thus user requests cannot succeed. In this case I think it'd be > preferable to relax the rpc timeout for meta requests so that a few long > requests can unblock many faster requests. > My suggestion would be to add an {{hbase.client.meta.rpc.timeout}} and ensure > that it applies to meta scans. I also think it would be less confusing to > have {{hbase.client.meta.operation.timeout}} apply as the scanner timeout > period for meta scans. -- This message was sent by Atlassian Jira (v8.20.10#820010)