[jira] [Commented] (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:comment-tabpanel=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)
[jira] [Commented] (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:comment-tabpanel=17369931#comment-17369931
]
Hudson commented on HBASE-26025:
Results for branch branch-2.3
[build #245 on
builds.a.o|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2.3/245/]:
(/) *{color:green}+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/branch-2.3/245/General_20Nightly_20Build_20Report/]
(/) {color:green}+1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2.3/245/JDK8_20Nightly_20Build_20Report_20_28Hadoop2_29/]
(/) {color:green}+1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2.3/245/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/branch-2.3/245/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}
> 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)
[jira] [Commented] (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:comment-tabpanel=17369884#comment-17369884
]
Hudson commented on HBASE-26025:
Results for branch master
[build #333 on
builds.a.o|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/master/333/]:
(/) *{color:green}+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/333/General_20Nightly_20Build_20Report/]
(/) {color:green}+1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/master/333/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/333/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}
> 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)
[jira] [Commented] (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:comment-tabpanel=17369779#comment-17369779
]
Hudson commented on HBASE-26025:
Results for branch branch-2.4
[build #152 on
builds.a.o|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2.4/152/]:
(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/branch-2.4/152/General_20Nightly_20Build_20Report/]
(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-2.4/152/JDK8_20Nightly_20Build_20Report_20_28Hadoop2_29/]
(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/branch-2.4/152/JDK8_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(x) {color:red}-1 jdk11 hadoop3 checks{color}
-- For more information [see jdk11
report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2.4/152/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}
> 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)
[jira] [Commented] (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:comment-tabpanel=17369642#comment-17369642
]
Hudson commented on HBASE-26025:
Results for branch branch-2
[build #287 on
builds.a.o|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2/287/]:
(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/branch-2/287/General_20Nightly_20Build_20Report/]
(/) {color:green}+1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2/287/JDK8_20Nightly_20Build_20Report_20_28Hadoop2_29/]
(/) {color:green}+1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2/287/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/branch-2/287/JDK11_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(x) {color:red}-1 client integration test{color}
-- Something went wrong with this stage, [check relevant console
output|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2/287//console].
> 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)
[jira] [Commented] (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:comment-tabpanel=17369351#comment-17369351 ] Yutong Xiao commented on HBASE-26025: - Yes I will push the branch-1 mr soon. > 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)
[jira] [Commented] (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:comment-tabpanel=17369350#comment-17369350 ] Reid Chan commented on HBASE-26025: --- Do you have plan for branch-1? [~xytss123] > 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)
[jira] [Commented] (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:comment-tabpanel=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)
