You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@shardingsphere.apache.org by GitBox <gi...@apache.org> on 2021/08/01 07:14:29 UTC
[GitHub] [shardingsphere] spilledyear opened a new issue #11593: Sharding-proxy may have problems in local transaction scenarios
spilledyear opened a new issue #11593:
URL: https://github.com/apache/shardingsphere/issues/11593
Scene description:
1. Same DB and sub-table
2. Set the value of maxConnectionsSizePerQuery greater than 1
3. Assuming that a logical SQL will be split into two physical SQLs, in the scenario where maxConnectionsSizePerQuery is greater than 1, two database connections will be created at this time. Two physical SQLs will eventually be executed in two database connections
4. Assuming that there is a query statement next, it is possible that the latest data cannot be obtained because of the wrong connection.
The core code is as follows:
ResourceManagedExecuteGroupEngine#generateSQLExecuteGroups
this is a demo:
--
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: notifications-unsubscribe@shardingsphere.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org