Skip to content

[4.4] Invalidate writers per database #1039

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 6 commits into from
Apr 12, 2024

Conversation

robsdedude
Copy link
Member

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).

Backport of: #959

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`).
Copy link
Contributor

@bigmontz bigmontz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🐢

@robsdedude robsdedude enabled auto-merge (squash) April 12, 2024 10:59
@robsdedude robsdedude merged commit 0823655 into neo4j:4.4 Apr 12, 2024
12 checks passed
@robsdedude robsdedude deleted the invalidate-writer-per-db-4.4 branch April 12, 2024 11: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