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

Remove server when failing on session acquisition #241

Merged

Conversation

pontusmelke
Copy link
Contributor

We were only checking for connection failures on running and consuming the
results, however there might also be a connection failure on session acquisition.
By not properly removing the server on session-acquisition failures we end up
in a scenario where we constantly retry to connect to that endpoint.

@pontusmelke pontusmelke added the bug label Oct 5, 2016
@pontusmelke pontusmelke force-pushed the 1.1-remove-address-on-connection-failure branch from 2badccc to f0045ee Compare October 5, 2016 11:04
We were only checking for connection failures on running and consuming the
results, however there might also be a connection failure on session acquisition.
By not properly removing the server on session-acquisition failures we end up
in a scenario where we constantly retry to connect to that endpoint.
@pontusmelke pontusmelke force-pushed the 1.1-remove-address-on-connection-failure branch from f0045ee to b4885f6 Compare October 5, 2016 11:18
@pontusmelke pontusmelke merged commit a81d882 into neo4j:1.1 Oct 5, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant