Skip to content

Discovery & Acquisition #227

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

Merged
merged 8 commits into from
Sep 13, 2016
Merged

Conversation

pontusmelke
Copy link
Contributor

No description provided.

@pontusmelke pontusmelke force-pushed the discovery-acquisition branch from 98048aa to d353ef7 Compare September 9, 2016 12:18
Instead of always throwing `ClientException` for connection failure we throw
a more specific, `ConnectionFailureException` so that the driver could better
recover from failures.
 By specifying `READ` or `WRITE` ClusterDriver will call procedure
 to get endpoints and creates a session using that connection.
@pontusmelke pontusmelke changed the title Discovery acquisition Discovery acquisition[NOT READY TO MERGE] Sep 12, 2016
For read session we do automatic retries since we know
the state of the database.
For write sessions we throw a SessionExpiredException on connection failures
@technige technige changed the title Discovery acquisition[NOT READY TO MERGE] Discovery & Acquisition Sep 13, 2016
@technige technige merged commit e47dcf6 into neo4j:1.1 Sep 13, 2016
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.

2 participants