[
https://issues.apache.org/jira/browse/HBASE-27078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17556535#comment-17556535
]
Bryan Beaudreault commented on HBASE-27078:
-------------------------------------------
Per discussion, I'm going to add new config
{{{}hbase.client.meta.scanner.timeout.period{}}}. This will solve the issue for
the async client. The branch-2 blocking client has an additional bug, which I
will tackle in https://issues.apache.org/jira/browse/HBASE-27142
> 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
> Priority: Major
>
> 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.7#820007)
