[
https://issues.apache.org/jira/browse/HBASE-27490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bryan Beaudreault updated HBASE-27490:
--------------------------------------
Fix Version/s: 2.6.0
> 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
> Assignee: Bryan Beaudreault
> Priority: Major
> Labels: patch-available
> Fix For: 2.6.0, 2.5.3
>
>
> 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)
