Skip to content

Introduce sessionConnectionTimeout and updateRoutingTableTimeout (#966) #967

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 1 commit into from
Jul 14, 2022

Conversation

bigmontz
Copy link
Contributor

sessionConnnectionTimeout is the maximum amount of time the session will wait when trying to establish a usable read/write connection to the remote host. This encompasses everything that needs to happen for this, including, if necessary, updating the routing table1, fetching a connection from the pool, and, if necessary performing a BOLT and Authentication handshake with the reader/writer.

updateRoutingTableTimeout is the maximum amount of time the driver will attempt to fetch a new routing table. This encompasses everything that needs to happen for this, including fetching connections from the pool, performing handshakes, and requesting and receiving a fresh routing table.

1Updating the routing table in turn might also require fetching a connection for the pool and performing the handshakes, plus potentially trying other routers.

@bigmontz
Copy link
Contributor Author

Cherry-picks: #966

…eo4j#966)

`sessionConnnectionTimeout` is the maximum amount of time the session will wait when trying to establish a usable read/write connection to the remote host. This encompasses *everything* that needs to happen for this, including, if necessary, updating the routing table<sup>1</sup>, fetching a connection from the pool, and, if necessary performing a BOLT and Authentication handshake with the reader/writer.

`updateRoutingTableTimeout` is the maximum amount of time the driver will attempt to fetch a new routing table. This encompasses *everything* that needs to happen for this, including fetching connections from the pool, performing handshakes, and requesting and receiving a fresh routing table.

<sup>1</sup>Updating the routing table in turn might also require fetching a connection for the pool and performing the handshakes, plus potentially trying other routers.
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.

1 participant