[
https://issues.apache.org/jira/browse/HBASE-28085?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17767845#comment-17767845
]
Hudson commented on HBASE-28085:
--------------------------------
Results for branch branch-2
[build #886 on
builds.a.o|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2/886/]:
(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/886/General_20Nightly_20Build_20Report/]
(/) {color:green}+1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2/886/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/886/JDK8_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {color:green}+1 jdk11 hadoop3 checks{color}
-- For more information [see jdk11
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2/886/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}
> Configurably use scanner timeout as rpc timeout for scanner next calls
> ----------------------------------------------------------------------
>
> Key: HBASE-28085
> URL: https://issues.apache.org/jira/browse/HBASE-28085
> Project: HBase
> Issue Type: Improvement
> Reporter: Bryan Beaudreault
> Assignee: Bryan Beaudreault
> Priority: Major
> Labels: patch-available
>
> In the AsyncTable implementation, scanner next() calls use
> "hbase.client.scanner.timeout.period" as the rpc timeout. The reason is
> described in comments, and makes a lot of sense:
> {code:java}
> // As we have a call sequence for scan, it is useless to have a different rpc
> timeout which is
> // less than the scan timeout. If the server does not respond in time(usually
> this will not
> // happen as we have heartbeat now), we will get an
> OutOfOrderScannerNextException when
> // resending the next request and the only way to fix this is to close the
> scanner and open a
> // new one. {code}
> The branch-2 HTable implementation still uses the old behavior – the next()
> call passes the read rpc timeout as the rpc timeout, and uses the scanner
> timeout period as the operation timeout. This can lead to the above behavior.
> It would be nice to provide users a migration path to AsyncTable's behavior,
> in the form of a config flag which causes HTable to use
> "hbase.client.scanner.timeout.period" as rpc timeout for next() calls like
> AsyncTable does.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
