Bug #19993 | ReplicationDriver always connects to a same slave server. | ||
---|---|---|---|
Submitted: | 22 May 2006 8:35 | Modified: | 26 Jul 2006 18:17 |
Reporter: | 俊夫 大矢 | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | Connector / J | Severity: | S2 (Serious) |
Version: | 3.1.12 | OS: | Any(Java) |
Assigned to: | CPU Architecture: | Any |
[22 May 2006 8:35]
俊夫 大矢
[3 Jul 2006 7:45]
Sveta Smirnova
Thank you for the report. Verified as reporter described using Connector/J 3.1.13. You can turn off last 2 slaves to be convinced what connection to first slave happens never.
[7 Jul 2006 4:50]
俊夫 大矢
Thank you for verifing this bug. I want to realize below behavior with MySQL Connector/J. -------- 1. Setting URL: jdbc:mysql://master,slave1,slave2,slave3/db Driver: com.mysql.jdbc.ReplicationDriver Props: roundRobinLoadBalance=true, autoReconnect=true 2. Expect Behavior First ReadOnly connection: connecting to 'slave1'. Second ReadOnly conncetion: connecting to 'slave2'. Third ReadOnly connection: connecting to 'slave3'. Forth ReadOnly connection: connecting to 'slave1'. ... ------------ This behavior is explained in MySQL Ref. Manual-'23.3.3.6. Using Master/Slave Replication with ReplicationConnection'. If that manual is correct, this bug should be fixed. If not, the manual should be fixed. Do you have any plan for this bug?
[19 Jul 2006 2:18]
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/9316