Skip to content
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

Attempt to stabilize BCCIT.shouldPickANewServerToWriteToOnLeaderSwitch #9162

Merged
merged 1 commit into from Apr 7, 2017
Merged

Attempt to stabilize BCCIT.shouldPickANewServerToWriteToOnLeaderSwitch #9162

merged 1 commit into from Apr 7, 2017

Conversation

digitalstain
Copy link
Contributor

It looks that the occasional failures of this test come from concurrent session
creation and switching of leaders. This is not a problem in real deployments,
but the fixed timeouts and specific requirements for leader election results
along with the constant composition of the cluster violate some assumptions
the test makes. This change ensures the leader switch that is needed completes
before any further action is taken, and also makes sure that no additional
elections are triggered during the session creations.

It looks that the occasional failures of this test come from concurrent session
 creation and switching of leaders. This is not a problem in real deployments,
 but the fixed timeouts and specific requirements for leader election results
 along with the constant composition of the cluster violate some assumptions
 the test makes. This change ensures the leader switch that is needed completes
 before any further action is taken, and also makes sure that no additional
 elections are triggered during the session creations.
@mneedham
Copy link
Contributor

mneedham commented Apr 6, 2017

This looks good to me.

@digitalstain digitalstain merged commit a3c6349 into neo4j:3.1 Apr 7, 2017
@digitalstain digitalstain deleted the 3.1-bolt-it-fix branch April 7, 2017 13:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants