You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Hudson (Jira)" <ji...@apache.org> on 2026/09/23 15:20:00 UTC
[jira] [Commented] (HBASE-30220) A replica cluster can have read-only mode disabled even when another active cluster already exists
[ https://issues.apache.org/jira/browse/HBASE-30220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18118401#comment-18118401 ]
Hudson commented on HBASE-30220:
--------------------------------
Results for branch branch-3
[build #163 on builds.a.o|https://ci-hbase.apache.org/job/HBase-Integration-Test/job/branch-3/163/]: (/) *{color:green}+1 overall{color}*
----
details (if available):
(/) {color:green}+1 client integration test for 3.3.5 {color}
(/) {color:green}+1 client integration test for 3.3.5 with shaded hadoop client{color}
(/) {color:green}+1 client integration test for 3.3.6 {color}
(/) {color:green}+1 client integration test for 3.3.6 with shaded hadoop client{color}
(/) {color:green}+1 client integration test for 3.4.0 {color}
(/) {color:green}+1 client integration test for 3.4.0 with shaded hadoop client{color}
(/) {color:green}+1 client integration test for 3.4.1 {color}
(/) {color:green}+1 client integration test for 3.4.1 with shaded hadoop client{color}
(/) {color:green}+1 client integration test for 3.4.2 {color}
(/) {color:green}+1 client integration test for 3.4.2 with shaded hadoop client{color}
(/) {color:green}+1 client integration test for 3.4.3 {color}
(/) {color:green}+1 client integration test for 3.4.3 with shaded hadoop client{color}
> A replica cluster can have read-only mode disabled even when another active cluster already exists
> --------------------------------------------------------------------------------------------------
>
> Key: HBASE-30220
> URL: https://issues.apache.org/jira/browse/HBASE-30220
> Project: HBase
> Issue Type: Bug
> Components: read replicas
> Reporter: Kevin Geiszler
> Assignee: Kevin Geiszler
> Priority: Major
> Labels: pull-request-available
>
> Assume you have a Read-Replica cluster setup where one cluster is the Active Cluster and the other cluster is a Replica Cluster with read-only mode enabled. Currently, it is possible to disable read-only mode on the Replica Cluster and end up with two clusters that allow writes. This should not happen.
> The steps to reproduce this are simple:
> # Start one cluster as the Active Cluster and another as the Replica Cluster
> # You should be able to create a table and add data on the Active Cluster but not on the Replica Cluster.
> # Change the {{hbase.global.readonly.enabled}} property from {{true}} to {{false}} on the Replica, save the conf file, and run {{update_all_config}}
> # Verify you can now create a table and add data on both clusters
--
This message was sent by Atlassian Jira
(v8.20.10#820010)