Repository navigation
Conversation
…re (apache#8517) - Changes were partially generated by Claude Opus 4.6
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
https://issues.apache.org/jira/browse/HBASE-30087
AI Usage
Some changes were generated using Claude Opus 4.6.
Summary
HBase's Read-Replica feature was merged into
masterin PR #8044. This pull request adds Jenkins integration tests for Read-Replica.The typical HBase mini-cluster integration test framework cannot be used to test the Read-Replica feature because each cluster in a read-replica setup must have a unique meta table name. These mini-clusters run in the same JVM and end up sharing the same static
META_TABLE_NAMEvariable. (PR #7730 is an open pull request to make the meta table name non-static.)Instead, these integration tests use two Docker containers running HBase that are part of a read-replica setup. An HBase Docker client uses Python to send HBase commands to the HBase shell within each container. This allows us to run each HBase cluster in its own isolated JVM.
The Read-Replica integration tests reside in
dev-support/read-replica. The tests have their ownJenkinsfilethat runs thehbase_nightly_read_replica_test.shdriver script, which does the following:dev-support/docker/Dockerfileand starts this container. The container helps with portability for running tests either locally or in Jenkins.Once the test environment container is up and running, the driver script runs
run_read_replica_integration_tests.shinside of this container, which does the following:docker compose. These containers are run alongside the test env container by bind-mounting the host's Docker socket (a Docker-outside-of-Docker (DooD) setup)pytestto run several integration testsThese integration tests have been run in Jenkins against this feature branch (HBASE-30087). We now would like to merge this feature branch to the master so the Read-Replica feature can continue to be tested against new changes to HBase.
Results Examples
Previous runs against the HBASE-30087 branch, including successful runs, can be found here:
https://ci-hbase.apache.org/job/HBase-Read-Replica-Tests/job/HBASE-30087/
Here is an example of a console report from a successful test run:
Here is an example of a failed run. When a test fails, the test's logs are linked along with the HBase logs from each read-replica Docker container: