[CONC-365] Failover capabilities Created: 2018-10-11  Updated: 2021-11-16  Resolved: 2021-11-12

Status: Closed
Project: MariaDB Connector/C
Component/s: None
Affects Version/s: None
Fix Version/s: 3.3.0

Type: New Feature Priority: Critical
Reporter: Ralf Gebhardt Assignee: Georg Richter
Resolution: Fixed Votes: 2
Labels: None

Issue Links:
Blocks
blocks CONCPP-4 Failover capabilities for Connector/C++ Closed
blocks CONPY-44 Failover capabilities for Connector/P... Closed
blocks ODBC-116 Failover capabilities for Connector/ODBC Closed
Relates
relates to CONC-529 Loadbalancing capabilities Open
relates to CONJS-169 Support failover and/or high-availabi... Closed
relates to R2DBC-21 Failover capabilities for Connector/R... Closed

 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.



 Comments   
Comment by Ralf Gebhardt [ 2018-10-11 ]

Blocker added as Connector/C needs to provide the functionality, Connector/ODBC will only need to provide functionality in the connection string.

Generated at Thu Feb 08 03:04:47 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.