Bug #97002 in failover, connectorJ does not connect when server SHUT-DOWN
Submitted: 25 Sep 6:44 Modified: 16 Nov 11:50
Reporter: Armache Antoni Email Updates:
Status: No Feedback Impact on me:
None 
Category:Connector / J Severity:S3 (Non-critical)
Version:8.0.17 OS:Any
Assigned to: CPU Architecture:Any

[25 Sep 6:44] Armache Antoni
Description:
Hi guys,

I have created a failover HA structures with replication on 2 server represented as Master/Master . 

this is my url link in my jdbc-driver : 

jdbc:mysql://192.168.153.110:3306,192.168.153.111:3306/romes?failOverReadOnly=false&secondsBeforeRetryMaster=0&queriesBeforeRetryMaster=0&retriesAllDown=1&autoReconnect=true&serverTimezone=UTC

Everyting is working perfectly, replication is implemented on both server, and when i turn off mysql.service with (sudo systemctl stop mysql.service) on server 192.168.153.110:3306 my jdbc driver switch the connection to 192.168.153.111:3306 with no duplication of primary key and HA is handled properly. The same goes from server 192.168.153.111:3306.

But i want to understand why when i SHUT-DOWN by force server 192.168.153.110:3306 ...... the switching is not happening ? why ?
the connection stay on locked on 192.168.153.110:3306.

How can i switch connection from 192.168.153.110:3306 to 192.168.153.111:3306
when SHUT-DOWN happen to server ?

Br.

Antoni 

How to repeat:
Implement Fail over and HA with Master/Master structures. and test it
[16 Oct 11:50] Alexander Soklakov
Hi Armache,

Could you give more details? How do you check which connection is active? Do you get any exceptions?
[17 Nov 1:00] Bugs System
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".