[ODBC-116] Failover capabilities for Connector/ODBC Created: 2017-09-28  Updated: 2022-06-27  Resolved: 2022-06-27

Status: Closed
Project: MariaDB Connector/ODBC
Component/s: General
Affects Version/s: None
Fix Version/s: 3.1.16

Type: New Feature Priority: Critical
Reporter: Chris Calender (Inactive) Assignee: Lawrin Novitsky
Resolution: Duplicate Votes: 0
Labels: None

Issue Links:
Blocks
is blocked by CONC-365 Failover capabilities Closed
Duplicate
duplicates ODBC-366 Add failover capability -> move to th... Closed
Relates
relates to CONPY-44 Failover capabilities for Connector/P... Closed
relates to ODBC-303 Please add load balancing to MariaDB ... Open
relates to R2DBC-21 Failover capabilities for Connector/R... Closed
relates to CONCPP-4 Failover capabilities for Connector/C++ 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 is focusing on failover, while ODBC-303 is covering the loadbalancing



 Comments   
Comment by Lawrin Novitsky [ 2017-12-01 ]

We've started to review the request and are look into functionality already provided by C/C

Comment by Lawrin Novitsky [ 2018-07-08 ]

1) Aurora plugin may be used as a good start - t's got many things of what we need, and doesn't rely a much on aurora-specific things
2) We need to make functionality and control interface as much like in C/J as possible
3) ODBC atm has limited means for control. The only thing we have for that is the connection string. We can get some more, if make connector to conform to the standard >=3.8, there driver-specific connection and statement attributes are allowed

Comment by Lawrin Novitsky [ 2022-06-27 ]

This has been added in 3.1.16 with the new ticket

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