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

Updated session acquisition #229

Merged
merged 14 commits into from
Sep 16, 2016
Merged

Updated session acquisition #229

merged 14 commits into from
Sep 16, 2016

Conversation

pontusmelke
Copy link
Contributor

@pontusmelke pontusmelke commented Sep 13, 2016

  • No retry on reads
  • bolt+routing
  • single procedure getServers to establish view of cluster

The plan of automatically handle retries on read sessions didn't really pan
out since we don't really control when data is transported over the network
and errors are noticed. Instead we treat reads and writes in the same way, i.e.
throwing a `SessionExpiredException` on all connection failures.
The connection pool is no longer responsible for maintaining the servers
since we must treat READ and WRITE servers differently. Instead added
a separate containers for the different server types.
Instead of two separate procedure calls, one to do routing and one to do
acquisition we merge them into one call containing the same information.
@pontusmelke pontusmelke changed the title Remove retry handling for read sessions Updated session acquisition Sep 15, 2016
@pontusmelke pontusmelke force-pushed the 1.1-acquisition branch 4 times, most recently from c67f8ba to b9212df Compare September 16, 2016 08:05
@technige technige merged commit 9858f73 into neo4j:1.1 Sep 16, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants