cqiwencom opened a new issue #11746:
URL: https://github.com/apache/shardingsphere/issues/11746
## Bug Report
### Which version of ShardingSphere did you use?
ShardingSphere-Proxy 5.0.0-beta
### Which project did you use? ShardingSphere-JDBC or ShardingSphere-Proxy?
ShardingSphere-Proxy
### Expected behavior
When executing 'select ... for update' , the select statement should be
routed to the writable node.
### Actual behavior
When executing 'select ... for update' , the select statement was routed to
the readable node.
### Reason analyze (If you can)
Proxy can't route 'select ... for update' to the writeable node
### Steps to reproduce the behavior, such as: SQL to execute, sharding rule
configuration, when exception occur etc.
schemaName: testdb
dataSources:
write_ds:
url: jdbc:mysql://127.0.0.1:6446/testdb?serverTimezone=UTC&useSSL=false
username: root
password: root
connectionTimeoutMilliseconds: 30000
idleTimeoutMilliseconds: 60000
maxLifetimeMilliseconds: 1800000
maxPoolSize: 50
minPoolSize: 1
read_ds_0:
url: jdbc:mysql://127.0.0.1:6447/testdb?serverTimezone=UTC&useSSL=false
username: root
password: root
connectionTimeoutMilliseconds: 30000
idleTimeoutMilliseconds: 60000
maxLifetimeMilliseconds: 1800000
maxPoolSize: 50
minPoolSize: 1
rules:
- !READWRITE_SPLITTING
dataSources:
pr_ds:
writeDataSourceName: write_ds
readDataSourceNames:
- read_ds_0
When executing 'select ... for update' , the select statement was routed to
read_ds_0. But in fact, this select statement should be routed to node write_ds.
--
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]
