Skip to content

Conversation

@lutovich
Copy link
Contributor

Previously driver considered routing table with single router to be stale and had to perform rediscovery before read/write transaction. Requirement to have more than 1 router is quite strict and can easily be violated by partially unavailable clusters. Additional rediscoveries in such cases add more load on the available core server.

This PR makes driver tread routing table with single router as not stale, given that other non-staleness requirements are satisfied as well.

Previously driver considered routing table with single router to be stale
and had to perform rediscovery before read/write transaction. Requirement
to have more than 1 router is quite strict and can easily be violated by
partially unavailable clusters. Additional rediscoveries in such cases
add more load on the available core server.

This commit makes driver tread routing table with single router as not
stale, given that other non-staleness requirements are satisfied as well.
@zhenlineo zhenlineo merged commit b8392d0 into neo4j:1.3 Apr 12, 2017
@lutovich lutovich deleted the 1.3-one-router-valid branch April 13, 2017 09:20
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