Python-IBM opened a new issue, #29661: URL: https://github.com/apache/shardingsphere/issues/29661
## Bug Report **For English only**, other languages will not accept. Before report a bug, make sure you have: - Searched open and closed [GitHub issues](https://github.com/apache/shardingsphere/issues). - Read documentation: [ShardingSphere Doc](https://shardingsphere.apache.org/document/current/en/overview). Please pay attention on issues you submitted, because we maybe need more details. If no response anymore and we cannot reproduce it on current information, we will **close it**. Please answer these questions before submitting your issue. Thanks! ### Which version of ShardingSphere did you use? 5.4.0 ### Which project did you use? ShardingSphere-JDBC or ShardingSphere-Proxy? ShardingSphere-JDBC ### Expected behavior I expect HikariCP to obtain the jdbcurl of the main MySQL ### Actual behavior HikariCP default to reading the jdbc of slave MySQL ### Reason analyze (If you can) Hikari generates 3 connection pools： 1、pool-1: **spring.datasource.url: jdbc:shardingsphere:apollo:account-jdbc** 2、pool-2: **dataSources.ds0.jdbcUrl: jdbc:mysql://192.168.1.101:3306/db_account** 3、pool-3: **dataSources.ds1.jdbcUrl: jdbc:mysql://192.168.1.101:3306/db_account_slave** HikariDataSource always reads the jdbcurl of pool-3 as the final result. ### Steps to reproduce the behavior, such as: SQL to execute, sharding rule configuration, when exception occur etc. (1) sharding rule configuration  (2)Causing the registration of RM resources in seata to always be the jdbcUrl of slave mysql  ### Example codes for reproduce this issue (such as a github link). -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
