You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hbase.apache.org by "Michael Stack (Jira)" <ji...@apache.org> on 2021/04/07 18:06:00 UTC

[jira] [Commented] (HBASE-25743) Retry REQUESTTIMEOUT KeeperExceptions from ZK

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

Michael Stack commented on HBASE-25743:
---------------------------------------

ZK 3.6 and 3.5.5 have the ZOOKEEPER-2251 commit. The PR changes OPERATIONTIMEOUT to do retry? Is this a change in behavior? Thanks [~bharathv]



> 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, 1.7.0, 2.5.0, 2.4.3, 2.3.6
>            Reporter: Bharath Vissapragada
>            Assignee: Bharath Vissapragada
>            Priority: Major
>
> 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)