I agree, everything works as expected but as long as the failover is not done (about 1 minute with our settings, we are using repmgr) we are unable to serve queries... I'd like the system to serve at least the reads in the meantime :)
If the preferMaster feature can be done "easily" at the driver level I take it.
Assuming that the old slave will become new master if master ever goes down then the option "master" would do what you want. Right?
But if you do take the master down for maintenance without failing over to slave then yes. A small code change could be done to add support for preferMaster.
I have a setup with 1 master and 1 slave (hot standy to serve read queries if necessary).
I would like the JDBC driver to talk preferrably to the master (to be sure to get the freshest data). If the master is not available I would like to send the queries to the slave.
The documentation mentions the following values for the parameter targetServerType: any, master, slave, preferSlave.
I'm surprised there is no preferMaster option which would allow me to implement easily my requirement.
