18511699755 commented on issue #6322: URL: https://github.com/apache/shardingsphere/issues/6322#issuecomment-658730977
I found the reason. spring.shardingsphere.props.max.connections.size.per.query=32 spring.shardingsphere.datasource.demo.max-active= 20 The two configurations are different. The former is larger than the latter. I have 256 tables here. When the shard key is not hit, all the tables will be scanned. According to the first configuration, 32 database connections will be created, but the database I configured here There are only 20 connections, and the creation process is synchronous, resulting in application process blocking. It is recommended that when this happens, the framework first judges the size of these two parameters and then selects the smallest one. ---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: [email protected]
