Skip to content

Invalidate writers per database #959

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
Aug 29, 2023

Conversation

robsdedude
Copy link
Member

@robsdedude robsdedude commented Aug 22, 2023

The driver now only removes a server as a writer for a single database (before
for all databases) if that server returns an error that notifies the driver that
the server is no longer a writer (Neo.ClientError.Cluster.NotALeader or
Neo.ClientError.General.ForbiddenOnReadOnlyDatabase).

Depends on:

This should improve the performance of the driver in multi database use-cases.
The driver now only removes a server as a writer for a single database (before
for all databases) if that server returns an error that notifies the driver that
the server is no longer a writer (`Neo.ClientError.Cluster.NotALeader` or
`Neo.ClientError.General.ForbiddenOnReadOnlyDatabase`).
@robsdedude robsdedude force-pushed the invalidate-writer-per-db branch from b559c40 to dddd315 Compare August 22, 2023 15:06
@robsdedude robsdedude merged commit 78b1e86 into neo4j:5.0 Aug 29, 2023
@robsdedude robsdedude deleted the invalidate-writer-per-db branch August 29, 2023 13:36
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