[
https://issues.apache.org/jira/browse/HBASE-30301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18100881#comment-18100881
]
Hudson commented on HBASE-30301:
--------------------------------
Results for branch master
[build #1480 on
builds.a.o|https://ci-hbase.apache.org/job/HBase%20Nightly/job/master/1480/]:
(x) *{color:red}-1 overall{color}*
----
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/master/1480/General_20Nightly_20Build_20Report/]
(x) {color:red}-1 jdk17 hadoop3 checks{color}
-- For more information [see jdk17
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/master/1480/JDK17_20Nightly_20Build_20Report_20_28Hadoop3_29/]
> Flush command hangs instead of failing for read-only clusters
> -------------------------------------------------------------
>
> Key: HBASE-30301
> URL: https://issues.apache.org/jira/browse/HBASE-30301
> Project: HBase
> Issue Type: Bug
> Components: read replicas
> Reporter: Kevin Geiszler
> Assignee: Kevin Geiszler
> Priority: Major
> Labels: pull-request-available
> Fix For: 4.0.0-alpha-1, 3.0.1
>
> Attachments: error.txt
>
>
> Assume you have a Read-Replica cluster setup where at least one cluster is a
> replica cluster with {{hbase.global.readonly.enabled}} set to {{{}false{}}}.
> Running {{flush}} on a table on this replica cluster results in the command
> hanging forever and the master log getting spammed with
> {{{}WriteAttemptedOnReadOnlyClusterException{}}}.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
