[
https://issues.apache.org/jira/browse/HBASE-26025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17370664#comment-17370664
]
Hudson commented on HBASE-26025:
--------------------------------
Results for branch branch-1
[build #139 on
builds.a.o|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-1/139/]:
(x) *{color:red}-1 overall{color}*
----
details (if available):
(x) {color:red}-1 general checks{color}
-- For more information [see general
report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-1/139//General_Nightly_Build_Report/]
(x) {color:red}-1 jdk7 checks{color}
-- For more information [see jdk7
report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-1/139//JDK7_Nightly_Build_Report/]
(x) {color:red}-1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-1/139//JDK8_Nightly_Build_Report_(Hadoop2)/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
> 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)
