[
https://issues.apache.org/jira/browse/HBASE-30087?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18118593#comment-18118593
]
Hudson commented on HBASE-30087:
--------------------------------
Results for branch HBASE-30087
[build #2 on
builds.a.o|https://ci-hbase.apache.org/job/HBase-Read-Replica-Nightly-Tests-2/job/HBASE-30087/2/]:
(x) *{color:red}-1 overall{color}*
----
details (if available):
(x) {color:red}-1 read-replica checks{color}
-- For more information [see read-replica test
report|https://ci-hbase.apache.org/job/HBase-Read-Replica-Nightly-Tests-2/job/HBASE-30087/2/Read_20Replica_20Nightly_20Test_20Report/]
> Create a nightly Jenkins test for the Read-Replica feature
> ----------------------------------------------------------
>
> Key: HBASE-30087
> URL: https://issues.apache.org/jira/browse/HBASE-30087
> Project: HBase
> Issue Type: Test
> Components: read replicas
> Reporter: Kevin Geiszler
> Assignee: Kevin Geiszler
> Priority: Major
> Labels: pull-request-available
>
> HBASE-29691 has still not been merged, which is blocking integration testing
> for the new Read-Replica feature (HBASE-29081).
> -As an alternate approach, we have started investigating using GitHub Actions
> to create two docker containers where one container is the active cluster and
> the other container is the read-replica cluster. We can use these containers
> to verify expected read-replica behavior.-
>
> After further investigation, it would be better to run the Read-Replica tests
> as part of HBase's nightly run with Jenkins rather than running them with
> GitHub Actions when a pull request has been submitted.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
