[ 
https://issues.apache.org/jira/browse/HBASE-25743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17317856#comment-17317856
 ] 

Hudson commented on HBASE-25743:
--------------------------------

Results for branch master
        [build #258 on 
builds.a.o|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/master/258/]:
 (x) *{color:red}-1 overall{color}*
----
details (if available):

(/) {color:green}+1 general checks{color}
-- For more information [see general 
report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/master/258/General_20Nightly_20Build_20Report/]






(x) {color:red}-1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3) 
report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/master/258/JDK8_20Nightly_20Build_20Report_20_28Hadoop3_29/]


(/) {color:green}+1 jdk11 hadoop3 checks{color}
-- For more information [see jdk11 
report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/master/258/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}


> Retry REQUESTTIMEOUT KeeperExceptions from ZK
> ---------------------------------------------
>
>                 Key: HBASE-25743
>                 URL: https://issues.apache.org/jira/browse/HBASE-25743
>             Project: HBase
>          Issue Type: Bug
>          Components: Zookeeper
>    Affects Versions: 3.0.0-alpha-1, 2.5.0, 2.4.3, 2.3.6
>            Reporter: Bharath Vissapragada
>            Assignee: Bharath Vissapragada
>            Priority: Major
>             Fix For: 3.0.0-alpha-1, 2.5.0, 2.4.3, 2.3.6
>
>
> Starting ZOOKEEPER-2251, client requests exceeding a timeout can throw a 
> KeeperException with REQUESTTIMEOUT opcode set. RecoverableZookeeper doesn't 
> transparently retry in such case. This was causing RS aborts when there is a 
> flaky ZK quorum member serving slow requests (especially in cases like 
> rolling upgrades and such).



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to