You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Bryan Beaudreault (Jira)" <ji...@apache.org> on 2022/11/16 20:07:00 UTC
[jira] [Updated] (HBASE-27490) Locating regions for all actions of batch requests can exceed operation timeout
[ https://issues.apache.org/jira/browse/HBASE-27490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bryan Beaudreault updated HBASE-27490:
--------------------------------------
Description:
This affects both AsyncTable and branch-2's Table. It's a follow-on from HBASE-27487.
In both cases, for a batch request, the first thing that must be done is resolve region locations for all actions in a batch. This is done in sequence for all actions, and the timeout is not checked after each action. If meta is slow or a sufficiently large batch is sent, the time to sequentially resolve all actions may exceed the operation timeout.
Currently, the code will eventually check the operation timeout after all locations have been resolved and before submitting the MultiRequests. We should check the timeout before each call to locate a region, and abort early if it's exceeded.
was:
This affects both AsyncTable and branch-2's Table. It's a follow-on from HBASE-27487.
In both cases, for a batch request, the first thing that must be done is resolve region locations for all actions in a batch. This is done in sequence for all actions, and the timeout is not checked after each action. If meta is slow or a sufficiently large batch is sent, the time to sequentially resolve all actions may exceed the operation timeout.
We should check the timeout before each call to locate a region, and abort early if it's exceeded.
> Locating regions for all actions of batch requests can exceed operation timeout
> -------------------------------------------------------------------------------
>
> Key: HBASE-27490
> URL: https://issues.apache.org/jira/browse/HBASE-27490
> Project: HBase
> Issue Type: Improvement
> Reporter: Bryan Beaudreault
> Priority: Major
>
> This affects both AsyncTable and branch-2's Table. It's a follow-on from HBASE-27487.
> In both cases, for a batch request, the first thing that must be done is resolve region locations for all actions in a batch. This is done in sequence for all actions, and the timeout is not checked after each action. If meta is slow or a sufficiently large batch is sent, the time to sequentially resolve all actions may exceed the operation timeout.
> Currently, the code will eventually check the operation timeout after all locations have been resolved and before submitting the MultiRequests. We should check the timeout before each call to locate a region, and abort early if it's exceeded.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)