[ 
https://issues.apache.org/jira/browse/HBASE-30220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18088082#comment-18088082
 ] 

Kevin Geiszler commented on HBASE-30220:
----------------------------------------

Here is an example log message from when the Replica Cluster becomes a second 
Active Cluster:
{noformat}
2026-06-10T16:03:33,676 INFO  
[RpcServer.priority.RWQ.Fifo.read.handler=4,queue=2,port=16000] 
util.CoprocessorConfigurationUtil: Updating coprocessors for Master 
hbase-docker-2,16000,1781107304082 because the configuration has changed
2026-06-10T16:03:33,676 INFO  
[RpcServer.priority.RWQ.Fifo.read.handler=4,queue=2,port=16000] 
util.CoprocessorConfigurationUtil: Config hbase.global.readonly.enabled has 
been dynamically changed to false for Master hbase-docker-2,16000,1781107304082
2026-06-10T16:03:33,677 DEBUG 
[RpcServer.priority.RWQ.Fifo.read.handler=4,queue=2,port=16000] 
access.AbstractReadOnlyController: Active cluster file already exists at: 
file:/data-store/hbase/active.cluster.suffix.id. No need to create it 
again.{noformat}

> 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
>
> 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)

Reply via email to