-
Notifications
You must be signed in to change notification settings - Fork 2.6k
Added MultiDbClient support with OSS Cluster API #3734
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: feat/active-active
Are you sure you want to change the base?
Conversation
…v-multi-db-client
…v-active-active-pipeline
…ement, fixed data structure
…v-active-active-pipeline
… into vv-pubsub-support
…v-active-active-pipeline
… into vv-pubsub-support
… into vv-pubsub-support
It seems that the pubsub changes for the standalone are part of this change together with the newly added sharded_pubsub changes and are causing conflicts. Other than that, the changes are looking good. |
sleep(0.1) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
0.1 might be too spamy on the logs, I usually do 0.5 or 1-3 seconds, but Idk if in your usecase its not 100% needed to be 0.1
) | ||
@pytest.mark.timeout(50) | ||
def test_pubsub_failover_to_another_db(self, r_multi_db, fault_injector_client): |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do you plan on doing multi? Idk if it's needed for the AA, but it might be helpful to discover issues? Maybe some blocking command. (I've not the same AA context as you, so feel free to ignore this comment.)
Pull Request check-list
Please make sure to review and check all of these items:
NOTE: these things are not required to open a PR and can be done
afterwards / while the PR is open.
Description of change
Please provide a description of the change here.