strongduanmu opened a new issue #13285: URL: https://github.com/apache/shardingsphere/issues/13285
## Bug Report ### Which version of ShardingSphere did you use? master branch ### Which project did you use? ShardingSphere-JDBC or ShardingSphere-Proxy? ShardingSphere-Proxy ### Expected behavior Read and write routing correctly ### Actual behavior select statement is routed to the write datasource  ### Reason analyze (If you can) ### Steps to reproduce the behavior, such as: SQL to execute, sharding rule configuration, when exception occur etc. First, configure db-discovery and readwrite-splitting according to the following configuration file. ```yaml schemaName: database_discovery_db dataSources: ds_0: url: jdbc:mysql://xxx/demo_primary_ds?serverTimezone=UTC&useSSL=false username: xxx password: xxx connectionTimeoutMilliseconds: 3000 idleTimeoutMilliseconds: 60000 maxLifetimeMilliseconds: 1800000 maxPoolSize: 50 minPoolSize: 1 ds_2: url: jdbc:mysql://xxx/demo_primary_ds?serverTimezone=UTC&useSSL=false username: xxx password: xxx connectionTimeoutMilliseconds: 3000 idleTimeoutMilliseconds: 60000 maxLifetimeMilliseconds: 1800000 maxPoolSize: 50 minPoolSize: 1 rules: - !READWRITE_SPLITTING dataSources: rd_rs: autoAwareDataSourceName: pr_ds - !DB_DISCOVERY dataSources: pr_ds: dataSourceNames: - ds_0 - ds_2 discoveryTypeName: mgr discoveryTypes: mgr: type: MGR props: groupName: b13df29e-90b6-11e8-8d1b-525400fc3996 zkServerLists: 'localhost:2181' keepAliveCron: '0/50 * * * * ?' ``` Then execute the following statement, you will get the wrong routing result. ```sql select * from t_address; ``` ### 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]
