public static interface ConnectionPoolConfiguration.Builder extends SdkPojo, CopyableBuilder<ConnectionPoolConfiguration.Builder,ConnectionPoolConfiguration>
| Modifier and Type | Method and Description |
|---|---|
ConnectionPoolConfiguration.Builder |
connectionBorrowTimeout(Integer connectionBorrowTimeout)
The number of seconds for a proxy to wait for a connection to become available in the connection pool.
|
ConnectionPoolConfiguration.Builder |
initQuery(String initQuery)
One or more SQL statements for the proxy to run when opening each new database connection.
|
ConnectionPoolConfiguration.Builder |
maxConnectionsPercent(Integer maxConnectionsPercent)
The maximum size of the connection pool for each target in a target group.
|
ConnectionPoolConfiguration.Builder |
maxIdleConnectionsPercent(Integer maxIdleConnectionsPercent)
Controls how actively the proxy closes idle database connections in the connection pool.
|
ConnectionPoolConfiguration.Builder |
sessionPinningFilters(Collection<String> sessionPinningFilters)
Each item in the list represents a class of SQL operations that normally cause all later statements in a
session using a proxy to be pinned to the same underlying database connection.
|
ConnectionPoolConfiguration.Builder |
sessionPinningFilters(String... sessionPinningFilters)
Each item in the list represents a class of SQL operations that normally cause all later statements in a
session using a proxy to be pinned to the same underlying database connection.
|
equalsBySdkFields, sdkFieldscopyapplyMutation, buildConnectionPoolConfiguration.Builder maxConnectionsPercent(Integer maxConnectionsPercent)
The maximum size of the connection pool for each target in a target group. For Aurora MySQL, it is expressed
as a percentage of the max_connections setting for the RDS DB instance or Aurora DB cluster used
by the target group.
Default: 100
Constraints: between 1 and 100
maxConnectionsPercent - The maximum size of the connection pool for each target in a target group. For Aurora MySQL, it is
expressed as a percentage of the max_connections setting for the RDS DB instance or
Aurora DB cluster used by the target group.
Default: 100
Constraints: between 1 and 100
ConnectionPoolConfiguration.Builder maxIdleConnectionsPercent(Integer maxIdleConnectionsPercent)
Controls how actively the proxy closes idle database connections in the connection pool. A high value enables
the proxy to leave a high percentage of idle connections open. A low value causes the proxy to close idle
client connections and return the underlying database connections to the connection pool. For Aurora MySQL,
it is expressed as a percentage of the max_connections setting for the RDS DB instance or Aurora
DB cluster used by the target group.
Default: 50
Constraints: between 0 and MaxConnectionsPercent
maxIdleConnectionsPercent - Controls how actively the proxy closes idle database connections in the connection pool. A high value
enables the proxy to leave a high percentage of idle connections open. A low value causes the proxy to
close idle client connections and return the underlying database connections to the connection pool.
For Aurora MySQL, it is expressed as a percentage of the max_connections setting for the
RDS DB instance or Aurora DB cluster used by the target group.
Default: 50
Constraints: between 0 and MaxConnectionsPercent
ConnectionPoolConfiguration.Builder connectionBorrowTimeout(Integer connectionBorrowTimeout)
The number of seconds for a proxy to wait for a connection to become available in the connection pool. Only applies when the proxy has opened its maximum number of connections and all connections are busy with client sessions.
Default: 120
Constraints: between 1 and 3600, or 0 representing unlimited
connectionBorrowTimeout - The number of seconds for a proxy to wait for a connection to become available in the connection pool.
Only applies when the proxy has opened its maximum number of connections and all connections are busy
with client sessions.
Default: 120
Constraints: between 1 and 3600, or 0 representing unlimited
ConnectionPoolConfiguration.Builder sessionPinningFilters(Collection<String> sessionPinningFilters)
Each item in the list represents a class of SQL operations that normally cause all later statements in a session using a proxy to be pinned to the same underlying database connection. Including an item in the list exempts that class of SQL operations from the pinning behavior.
Default: no session pinning filters
sessionPinningFilters - Each item in the list represents a class of SQL operations that normally cause all later statements in
a session using a proxy to be pinned to the same underlying database connection. Including an item in
the list exempts that class of SQL operations from the pinning behavior.
Default: no session pinning filters
ConnectionPoolConfiguration.Builder sessionPinningFilters(String... sessionPinningFilters)
Each item in the list represents a class of SQL operations that normally cause all later statements in a session using a proxy to be pinned to the same underlying database connection. Including an item in the list exempts that class of SQL operations from the pinning behavior.
Default: no session pinning filters
sessionPinningFilters - Each item in the list represents a class of SQL operations that normally cause all later statements in
a session using a proxy to be pinned to the same underlying database connection. Including an item in
the list exempts that class of SQL operations from the pinning behavior.
Default: no session pinning filters
ConnectionPoolConfiguration.Builder initQuery(String initQuery)
One or more SQL statements for the proxy to run when opening each new database connection. Typically used
with SET statements to make sure that each connection has identical settings such as time zone
and character set. For multiple statements, use semicolons as the separator. You can also include multiple
variables in a single SET statement, such as SET x=1, y=2.
Default: no initialization query
initQuery - One or more SQL statements for the proxy to run when opening each new database connection. Typically
used with SET statements to make sure that each connection has identical settings such as
time zone and character set. For multiple statements, use semicolons as the separator. You can also
include multiple variables in a single SET statement, such as SET x=1, y=2.
Default: no initialization query
Copyright © 2021. All rights reserved.