[CONJ-547] Aurora failover based on read replica priority Created: 2017-11-06  Updated: 2023-12-14  Resolved: 2023-12-14

Status: Closed
Project: MariaDB Connector/J
Component/s: aurora, Failover
Affects Version/s: None
Fix Version/s: N/A

Type: Bug Priority: Trivial
Reporter: Sumitro Palit Assignee: Diego Dupin
Resolution: Won't Do Votes: 0
Labels: aurora


 Description   

Aurora read replicas can be set up with different failover priorities (Tier0 – Tier9 ...).
Can the failover logic in the driver be modified to detect the read replica with higher priority (Tier0 over Tier 1 over Tier 2 ....) and switch writes to that read node.
In our initial tests we are seeing that to be up faster than when the failover is reported as complete on the cluster (seconds instead of 10s of seconds) - so there might be some value there but we need more tests to confirm.
That way the effective failover time might be faster than what is reported by Aurora.
If there are multiple read nodes with the same priority we might have to cycle through them - so it might be slightly more complex.


This might be a custom code on our side and not a generic fix.
However, it will be good to know if someone else have tried anything along these lines.



 Comments   
Comment by Diego Dupin [ 2023-12-14 ]

aurora is in maintenance mode for 2.x and not supported anymore in 3.x version, so closing feature request

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