Details
-
New Feature
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Won't Do
-
None
Description
Currently, on Galera clusters the most commonly used router is read-write split, which only sends the writes to one of the nodes. One of the advantages of Galera is the full write support on all nodes, so it would be very useful to have a router which could route the write requests to all nodes.
One way to do this would be to open a connection to only one of the Galera nodes for each incoming session; then all traffic from this session goes to the chosen node. The choice of the node could be a simple round-robin, or, optionally, a some more advanced algorithm based on the number of open sessions to each node.
This has proven to be a misconception among users: our research suggests that writing to multiple Galera nodes does not increase the scalability of writes and only leads to deadlock errors on commit.
This configuration is possible right now with the readconnroute router with the router_options parameter set to synced but we don't recommend it due to the changes that are required to the application logic.