[
https://issues.apache.org/jira/browse/HBASE-26025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17369349#comment-17369349
]
Reid Chan commented on HBASE-26025:
-----------------------------------
Pushed to master, branch-2.
>From branch-2, cherry-picked to branch-2.3 & branch-2.4
> 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, 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)