[
https://issues.apache.org/jira/browse/HBASE-19695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16745834#comment-16745834
]
Hudson commented on HBASE-19695:
--------------------------------
Results for branch branch-2.1
[build #782 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.1/782/]:
(x) *{color:red}-1 overall{color}*
----
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.1/782//General_Nightly_Build_Report/]
(/) {color:green}+1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.1/782//JDK8_Nightly_Build_Report_(Hadoop2)/]
(x) {color:red}-1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.1/782//JDK8_Nightly_Build_Report_(Hadoop3)/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(/) {color:green}+1 client integration test{color}
> Handle disabled table for async client
> --------------------------------------
>
> Key: HBASE-19695
> URL: https://issues.apache.org/jira/browse/HBASE-19695
> Project: HBase
> Issue Type: Sub-task
> Components: asyncclient, Client
> Reporter: Duo Zhang
> Assignee: Duo Zhang
> Priority: Major
> Fix For: 3.0.0, 2.2.0, 2.1.3, 2.0.5
>
> Attachments: HBASE-19695-v1.patch, HBASE-19695-v2.patch,
> HBASE-19695.master.001.patch, HBASE-19695.master.002.patch, HBASE-19695.patch
>
>
> Now for async client we will not check if a table is disabled when retrying,
> so we will retry until the time or count limit is reached, and will not throw
> a TableNotEnabledException.
> We should have the same behavior as sync client, but the implementation
> should be carefully designed. For sync client, we will also check if a table
> is disabled if it is a retry, no matter what the exception is. This will
> double the pressure on meta table. We should try our best to eliminate
> unnecessary access to meta table.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
