-
Notifications
You must be signed in to change notification settings - Fork 6.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Execute engine enhancement #1205
Labels
Comments
This was referenced Aug 29, 2018
Closed
terrymanu
added a commit
that referenced
this issue
Sep 1, 2018
terrymanu
added a commit
that referenced
this issue
Sep 1, 2018
terrymanu
added a commit
that referenced
this issue
Sep 1, 2018
terrymanu
added a commit
that referenced
this issue
Sep 1, 2018
terrymanu
added a commit
that referenced
this issue
Sep 1, 2018
terrymanu
added a commit
that referenced
this issue
Sep 1, 2018
terrymanu
added a commit
that referenced
this issue
Sep 1, 2018
terrymanu
added a commit
that referenced
this issue
Sep 1, 2018
terrymanu
added a commit
that referenced
this issue
Sep 2, 2018
terrymanu
added a commit
that referenced
this issue
Sep 18, 2018
terrymanu
added a commit
that referenced
this issue
Sep 18, 2018
terrymanu
added a commit
that referenced
this issue
Sep 19, 2018
terrymanu
added a commit
that referenced
this issue
Sep 19, 2018
terrymanu
added a commit
that referenced
this issue
Sep 19, 2018
terrymanu
added a commit
that referenced
this issue
Sep 20, 2018
… for get connections on same data source, because data source map always use same hash sequence to iterator entries
terrymanu
changed the title
Optimize and simplify MEMORY_STRICTLY & CONNECTION_STRICTLY model
Execute engine enhancement
Sep 23, 2018
terrymanu
added a commit
that referenced
this issue
Sep 23, 2018
terrymanu
added a commit
that referenced
this issue
Sep 23, 2018
terrymanu
added a commit
that referenced
this issue
Sep 23, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
max.connections.size.per.query
to control concurrency for database access on CONNECTION_STRICTLY modelmax.connections.size.per.query
greater than table routed count, use MEMORY_STRICTLY automaticallymax.connections.size.per.query
must less or equal to maximumPoolSize in Sharding-Proxy (Sharding-JDBC cannot check because of connection pool is provided by end user)max.connections.size.per.query
to switch model smartlyThe text was updated successfully, but these errors were encountered: