[
https://issues.apache.org/jira/browse/HBASE-25293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17252262#comment-17252262
]
Hudson commented on HBASE-25293:
--------------------------------
Results for branch branch-2.4
[build #12 on
builds.a.o|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2.4/12/]:
(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/12/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.4/12/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/12/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.4/12/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}
> Followup jira to address the client handling issue when chaning from meta
> replica to non-meta-replica at the server side.
> -------------------------------------------------------------------------------------------------------------------------
>
> Key: HBASE-25293
> URL: https://issues.apache.org/jira/browse/HBASE-25293
> Project: HBase
> Issue Type: Sub-task
> Reporter: Huaxiang Sun
> Assignee: Huaxiang Sun
> Priority: Minor
>
> [https://github.com/apache/hbase/pull/2643]
>
> {quote}
> With my operator hat on, I'd assume that LOAD_BALANCE with 1 replica count
> works like no read replicas configured (logic wise at-least, even though the
> code paths are different).
> {quote}If the server side does not support meta replica, the client side
> cannot be configured to support this mode
> {quote}
> Since clients are usually long running (meaning we may not be able to restart
> client or they using cached HBase connection) and meta replica count can be
> altered on the service side on the fly, I'd expect client to work across
> these changes without any configuration changes. WDYT?
> {quote}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
