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 2020/07/10 09:54:33 UTC
[GitHub] [shardingsphere] 18511699755 opened a new issue #6322: The database connection cannot be released without using the slice key when adding or querying data
18511699755 opened a new issue #6322:
URL: https://github.com/apache/shardingsphere/issues/6322
When adding or querying data, the database connection cannot be released without using the slicing key, and sql execution also fails
----------------------------------------------------------------
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:
users@infra.apache.org
[GitHub] [shardingsphere] kimmking commented on issue #6322: The database connection cannot be released without using the slice key when adding or querying data
Posted by GitBox <gi...@apache.org>.
kimmking commented on issue #6322:
URL: https://github.com/apache/shardingsphere/issues/6322#issuecomment-656616407
details such as config rules, logic sql and actual sql .
----------------------------------------------------------------
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:
users@infra.apache.org
[GitHub] [shardingsphere] 18511699755 commented on issue #6322: The database connection cannot be released without using the slice key when adding or querying data
Posted by GitBox <gi...@apache.org>.
18511699755 commented on issue #6322:
URL: https://github.com/apache/shardingsphere/issues/6322#issuecomment-656603407
$ curl 127.0.0.1:8085/t
The command will be blocked after execution
There are 256 tables, and there will be 256 Actual SQL, but if there is no SQL execution result, it will be reported that the database link is insufficient if CURL is carried out many times
----------------------------------------------------------------
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:
users@infra.apache.org
[GitHub] [shardingsphere] 18511699755 removed a comment on issue #6322: The database connection cannot be released without using the slice key when adding or querying data
Posted by GitBox <gi...@apache.org>.
18511699755 removed a comment 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:
users@infra.apache.org
[GitHub] [shardingsphere] kimmking commented on issue #6322: The database connection cannot be released without using the slice key when adding or querying data
Posted by GitBox <gi...@apache.org>.
kimmking commented on issue #6322:
URL: https://github.com/apache/shardingsphere/issues/6322#issuecomment-656600240
can you show more details?
----------------------------------------------------------------
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:
users@infra.apache.org
[GitHub] [shardingsphere] 18511699755 closed issue #6322: The database connection cannot be released without using the slice key when adding or querying data
Posted by GitBox <gi...@apache.org>.
18511699755 closed issue #6322:
URL: https://github.com/apache/shardingsphere/issues/6322
----------------------------------------------------------------
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:
users@infra.apache.org
[GitHub] [shardingsphere] 18511699755 commented on issue #6322: The database connection cannot be released without using the slice key when adding or querying data
Posted by GitBox <gi...@apache.org>.
18511699755 commented on issue #6322:
URL: https://github.com/apache/shardingsphere/issues/6322#issuecomment-659364781
> details such as config rules, logic sql and actual sql .
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:
users@infra.apache.org
[GitHub] [shardingsphere] 18511699755 commented on issue #6322: The database connection cannot be released without using the slice key when adding or querying data
Posted by GitBox <gi...@apache.org>.
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:
users@infra.apache.org