Bug #23281 Connections starting up failed-over (due to down slave) never retry master
Submitted: 13 Oct 2006 21:28 Modified: 13 Oct 2006 21:36
Reporter: Tonci Grgin Email Updates:
Status: Closed Impact on me:
None 
Category:Connector / J Severity:S3 (Non-critical)
Version:3.1, 5.0 OS:
Assigned to: Mark Matthews CPU Architecture:Any

[13 Oct 2006 21:28] Tonci Grgin 
Description:
Driver would not advance to next host if roundRobinLoadBalance=true and the last host in the list is down.

How to repeat:
 - Set up two machines, S1 and S2.
 - Set up connection properties as "roundRobinLoadBalance=true,failOverReadOnly=false&autoreconnect=true"
 - Set the connection URL as
jdbc:mysql://S1:port1,S2:port2/schema/?user=xxx&password=xxx&failOverReadOnly=false&roundRobinLoadBalance=true
 - Start S1, S2 is *NOT* running
 - Second connection never tries S1 thus failing
[19 Oct 2006 15:40] Bugs System 
A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/commits/13999