Details
-
New Feature
-
Status: Closed (View Workflow)
-
Critical
-
Resolution: Fixed
-
None
-
None
-
None
Description
Goal is to permit setting some failover capability on connector level.
Configuration must permit setting multiple hosts/ports. Then, when trying to establish a connection, connector will trying to connect those hosts sequentially until success or throwing error if last host connection fails.
This would permit failover on multiple maxscale instances, avoiding use additional tools that monitor maxscales state.
"failover" in the scope of this task is trying hosts from the list of alternative hosts until connection succeeds. It should work on the first connect and on auto-reconnect. Nothing else is in the scope, no replaying of transactions, for example.
Attachments
Issue Links
- blocks
-
CONCPP-4 Failover capabilities for Connector/C++
- Closed
-
CONPY-44 Failover capabilities for Connector/Python
- Closed
-
ODBC-116 Failover capabilities for Connector/ODBC
- Closed
- relates to
-
CONC-529 Loadbalancing capabilities
- Open
-
CONJS-169 Support failover and/or high-availability/load-balancing from Node.JS connector
- Closed
-
R2DBC-21 Failover capabilities for Connector/R2DBC
- Closed
- mentioned in
-
Page Loading...