[CONPY-44] Failover capabilities for Connector/Python Created: 2020-03-13  Updated: 2022-04-13  Resolved: 2022-01-23

Status: Closed
Project: MariaDB Connector/Python
Component/s: DBAPI 2.0
Affects Version/s: None
Fix Version/s: 1.1.0rc1

Type: New Feature Priority: Major
Reporter: Geoff Montee (Inactive) Assignee: Georg Richter
Resolution: Fixed Votes: 2
Labels: None

Issue Links:
Blocks
is blocked by CONC-365 Failover capabilities Closed
Relates
relates to CONPY-146 Loadbalancing capabilities for Connec... Open
relates to CONCPP-4 Failover capabilities for Connector/C++ Closed
relates to ODBC-116 Failover capabilities for Connector/ODBC 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.

UPDATE: This task would cover the failover, CONPY-146 the loadbalancing

The feature itself is provided by MariaDB Connector/C 3.3 - CONC-365

  • For Windows, MariaDB Connector/C 3.3 is linked statically with this release
  • For Linux, MariaDB Connector/C 3.3 needs to be installed
    • Tests have been added
  • The host argument for function mariadb.connect can be specified as a comma-separated list containing multiple server addresses

 Comments   
Comment by Georg Richter [ 2022-01-23 ]

This issue was fixed by implementation of CONC-365. If MariaDB Connector/Python uses MariaDB Connector/C < 3.3.0 an exception will be raised if multiple hosts were specified in host parameter (rev. 63c82019ab46191c0ccb476872a4048da954a120)

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