-
Notifications
You must be signed in to change notification settings - Fork 8
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
[Cluster.NotALeader] No write operations are allowed directly on this database. Writes must pass through the leader #932
Comments
We have the same issue with |
How are you running the query? |
Thank for answering, @technige! This is how we run the query: We have a Model
We have a Graph:
|
We have this error in both |
This is complete example of failing code. This code is failing with the latest
|
@kostia-sukernik and I are talking about another issue, the error we see after running write queries is different:
But with the official |
I can only confirm that when I run query your way I have the same issue:
|
I can confirm that when setting up a cluster through docker using the official image I get the ` My conf file:
The Docker compose file:
|
@technige technige We are also facing the same issue (py2neo.errors.WriteServiceUnavailable) after switching to cluster and enabling routing, could you please give any insight on this?
Neo4j's official driver is not giving any error. Thank you for this wonderful library. |
@technige Could you please provide some insight ? @SimonThordal @abronin @RazLightlytics @kostia-sukernik was wondering if you guys found any solution? |
Hi,
I am getting this exception when running a write query against a neo4j causal cluster version 4.3.6, this work fine with causal cluster of version 4.1.1. In both cases the query is sent to a follower server, py2neo is 2021.2.3.
Graph is initialized using:
Graph('neo4j://<dns_address>:7687', **settings)
settings:
{'user': 'neo4j', 'password': password, 'name': <db_name>, 'routing': True, 'routing_refresh_ttl': 300}
Any idea what can cause this behavior?
Thanks
The text was updated successfully, but these errors were encountered: