Clusters and routing

The Cypher Transactional API provides a limited level of support for query routing.

The level of support depends on whether Server-side routing has been enabled:

Server-side routing Support

Server-side routing	Support
`disabled`	Clusters support read-only queries.
`enabled`	Clusters support routing for queries that involve a single request (i.e. via the `tx/commit` endpoint). This is because the cluster does not currently support transaction identifiers across the cluster. By default, all transactions are considered `WRITE` transactions, even if they contain no Cypher with write operations. This can be overridden by setting a value of `READ` in the `access-mode` header of the request (For more information, see Transaction Configuration - Access Mode). This default value ensures that all queries are ultimately run on the leader. To ensure efficient load balancing of `READ` transactions, you should label them as such in the request.

disabled

Clusters support read-only queries.

enabled

Clusters support routing for queries that involve a single request (i.e. via the tx/commit endpoint). This is because the cluster does not currently support transaction identifiers across the cluster.

By default, all transactions are considered WRITE transactions, even if they contain no Cypher with write operations. This can be overridden by setting a value of READ in the access-mode header of the request (For more information, see Transaction Configuration - Access Mode).

This default value ensures that all queries are ultimately run on the leader. To ensure efficient load balancing of READ transactions, you should label them as such in the request.

Was this page helpful?