You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I couldn't find a definitive answer in the documentation, but it seems that routing does not take place when using the bolt protocol, not even when the routing is expected to take place on the server.
When using the neo4j:// protocol the reported issue does not occur. If server side routing is not intended to work with the bolt:// protocol this issue can be closed.
@JorgenEvens Correct, server-side routing is not performed when using the bolt scheme.
Neo4j Drivers can only use server-side routing when the neo4j:// URI scheme is used. The Drivers do not perform any routing when the bolt:// URI scheme is used, instead connecting directly to the specified host.
-lb-neo4j
loadbalancercreate database mytest
Neo.ClientError.Cluster.NotALeader
errorcall dbms.cluster.routing.getRoutingTable({ database: 'mytest' })
show database mytest
Neo.ClientError.Cluster.NotALeader
errorshow database
.Debug logs of the three nodes:
neo4j-persona-0-0_debug.log
neo4j-persona-1-0_debug.log
neo4j-persona-2-0_debug.log
The text was updated successfully, but these errors were encountered: