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

Posted to issues@hbase.apache.org by "Reid Chan (Jira)" <ji...@apache.org> on 2021/06/28 02:27:00 UTC

[jira] [Resolved] (HBASE-26025) Add a flag to mark if the IOError can be solved by retry in thrift IOError

     [ https://issues.apache.org/jira/browse/HBASE-26025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Reid Chan resolved HBASE-26025.
-------------------------------
    Hadoop Flags: Reviewed
      Resolution: Resolved

> Add a flag to mark if the IOError can be solved by retry in thrift IOError
> --------------------------------------------------------------------------
>
>                 Key: HBASE-26025
>                 URL: https://issues.apache.org/jira/browse/HBASE-26025
>             Project: HBase
>          Issue Type: Improvement
>          Components: Thrift
>            Reporter: Yutong Xiao
>            Assignee: Yutong Xiao
>            Priority: Major
>             Fix For: 3.0.0-alpha-1, 2.5.0, 2.3.6, 1.7.1, 2.4.5
>
>
> Currently, if an HBaseIOException occurs, the thrift client can only get the error message. This is inconvenient for the client constructing a retry mechanism to handle the exception. So I added a canRetry mark in IOError to make the client side exception handling smarter.



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