GitHub is home to over 20 million developers working together to host and review code, manage projects, and build software together.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
Already on GitHub? Sign in to your account
In the first test, test_connect_and_manual_refresh_with_secondary_down, I'm stopping only one secondary as opposed to all of them so that the primary doesn't step itself down and become a secondary. I assert that the number of secondaries has decreased by one after a refresh.
In the second test, test_automated_refresh_with_secondary_down, I stop the secondary that has been pinned for reads. Then I assert that the version and read pool change after an automatic refresh.
RUBY-558 apply batch size on initial query
RUBY-505 test on intervening query during cursor iteration
Merge remote-tracking branch 'upstream/master'
minor: further fix race condition in refresh test