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
Copy file name to clipboardExpand all lines: modules/ROOT/pages/clustering/setup/routing.adoc
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -42,7 +42,7 @@ Client-side routing means that the application decides which cluster server to s
42
42
Typically, this ensures that write operations are sent to the server currently acting as the `writer` for the target database, while read operations are sent to other servers.
43
43
44
44
Client-side routing is based on getting a routing table from a cluster server, and then using that information to make the routing decisions.
45
-
Use the xref:procedures.adoc#procedure_dbms_routing_getRoutingTable[`dbms.routing.getRoutingTable()`] procedure to obtain a routing table.
45
+
Use the xref:procedures/built-in-procedures.adoc#procedure_dbms_routing_getRoutingTable[`dbms.routing.getRoutingTable()`] procedure to obtain a routing table.
46
46
47
47
A routing table contains information about the servers and their roles as `writers`, `readers`, and `routers` for a specific database.
48
48
There is usually one `writer`, though there may be none if the database is read-only or unhealthy.
0 commit comments