Failover in reactive MySQL connection

[volkland]

We use the Reactive MySQL client in Quarkus 3 and want to implement a failover behaviour between our two datacenter set-ups. Each datacenter hosts the application and the MySQL database, and currently each instance of the app is only connected to its own datacenter's database.

We want to configure our Quarkus app so that the client primarily uses the DB in its own datacenter, and only if that becomes unavailable, switches to the DB in the other datacenter.

We have tried the Load-balancing configuration, but that seems to be implemented like a round-robin.
With this setting, we would create unnecessary round-trips between our datacenters.

Is there a way to prioritize the database connections inside Quarkus or have a form of failover mechanism?

Thanks for your help and Best Regards.