There are two kinds of Bolt drivers specified by URI scheme: the bolt:// scheme is used to create a direct driver and the bolt+routing:// scheme is used to create a routing driver.
Neo4j Browser will always:
- Use a direct driver for user administration frames
- Use a direct driver to populate :sysinfo and the member specific items in the information panel e.g. version, cluster role etc
When using bolt+routing and the provided URI points to a Core Causal Cluster member Neo4j Browser will:
- Use a routing driver for all cypher queries submitted via the editor (including calls to user admininstration procedures)
- Use a routing driver to populate the metadata (labels, relationship types, properties) in the information panel
If the provided URI points to a Read-Replica Causal Cluster member, Neo4j Browser will:
- Use a direct driver for all cypher queries submitted via the editor
- Use a direct driver to populate the metadata (labels, relationship types, properties) in the information panel
Please note that in order for bolt+routing to work correctly the current user must exist on all members in the cluster with the same authentication credentials.
Failed to Establish Connection in (5000)ms.
When a driver attempts to connect to the server, it has a default amount of time that it will wait for a response from the server before giving up. When you get this message, it generally means that you did make a connection to the server, but the server isn’t responsive within that timeout window. It may not be 5000ms, this is a configurable driver setting, and will depend on which language driver you’re using, and your local configuration.
A common reason why this error occurs is that your Neo4j instance is under heavy load. For example if you’re running a query that is soon going to result in an Out of Memory error, it would be possible to run into this error. Another possibility is extremely high network latency between your machine and the Neo4j instance, for example if you’re on a low quality wifi link.