This is an automated email from the ASF dual-hosted git repository.
zykkk pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/doris-website.git
The following commit(s) were added to refs/heads/master by this push:
new cd979ea0da4 improve jdbc catalog connection pool doc (#1194)
cd979ea0da4 is described below
commit cd979ea0da402e80cb9ac4e004b5370735623dba
Author: zy-kkk <zhongy...@gmail.com>
AuthorDate: Tue Oct 15 14:39:25 2024 +0800
improve jdbc catalog connection pool doc (#1194)
---
docs/lakehouse/database/jdbc.md | 56 ++++++++++---------
.../current/lakehouse/database/jdbc.md | 54 +++++++++---------
.../version-2.0/lakehouse/database/jdbc.md | 65 ++++++++++++++--------
.../version-2.1/lakehouse/database/jdbc.md | 34 ++++++++---
.../version-3.0/lakehouse/database/jdbc.md | 58 +++++++++----------
.../version-2.0/lakehouse/database/jdbc.md | 65 ++++++++++++++--------
.../version-2.1/lakehouse/database/jdbc.md | 65 ++++++++++++++--------
.../version-3.0/lakehouse/database/jdbc.md | 54 +++++++++---------
8 files changed, 261 insertions(+), 190 deletions(-)
diff --git a/docs/lakehouse/database/jdbc.md b/docs/lakehouse/database/jdbc.md
index 803a468bf57..2363054c14c 100644
--- a/docs/lakehouse/database/jdbc.md
+++ b/docs/lakehouse/database/jdbc.md
@@ -69,7 +69,7 @@ Doris JDBC Catalog supports connecting to the following
databases:
| Parameter | Default value | Description
|
|---------------------------------|----------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| `connection_pool_min_size` | 1 | Defines the minimum
number of connections in the connection pool, which is used to initialize the
connection pool and ensure that at least this number of connections are active
when the keep-alive mechanism is enabled.
|
-| `connection_pool_max_size` | 10 | Defines the maximum
number of connections in the connection pool. Each FE or BE node corresponding
to each Catalog can hold up to this number of connections.
|
+| `connection_pool_max_size` | 30 | Defines the maximum
number of connections in the connection pool. Each FE or BE node corresponding
to each Catalog can hold up to this number of connections.
|
| `connection_pool_max_wait_time` | 5000 | Defines the maximum
number of milliseconds the client will wait for a connection if there is no
available connection in the connection pool.
|
| `connection_pool_max_life_time` | 1800000 | Set the maximum time (in
milliseconds) that a connection remains active in the connection pool. Timed
out connections will be recycled. At the same time, half of this value will
serve as the minimum eviction idle time of the connection pool, and connections
that reach this time will become eviction candidates. |
| `connection_pool_keep_alive` | false | Only valid on BE nodes,
used to decide whether to keep connections that have reached the minimum
eviction idle time but have not reached the maximum lifetime active. Turned off
by default to reduce unnecessary resource usage.
|
@@ -319,29 +319,31 @@ Through the `CALL EXECUTE_STMT()` command, Doris will
directly send the SQL stat
## Troubleshooting connection pool issues
-1. In versions less than 2.0.5, the connection pool related configuration can
only be configured in JAVA_OPTS of BE conf, refer to version 2.0.4
[be.conf](https://github.com/apache/doris/blob/ 2.0.4-rc06/conf/be.conf#L22).
-2. In versions 2.0.5 and later, connection pool related configurations can be
configured in the Catalog properties, refer to [Connection Pool
Properties](#Connection Pool Properties).
-3. The connection pool used by Doris was changed from Druid to HikariCP
starting from 2.0.10 (2.0 Release) and 2.1.3 (2.1 Release), so the connection
pool related errors and troubleshooting methods are different, refer to the
following
-
-* Druid connection pool version
- * Initialize datasource failed: CAUSED BY: GetConnectionTimeoutException:
wait millis 5006, active 10, maxActive 10, creating 1
- * Reason 1: Too many queries cause the number of connections to exceed
the configuration
- * Reason 2: The connection pool count is abnormal and the active count
does not decrease.
- * Solution
- * alter catalog <catalog_name> set properties
('connection_pool_max_size' = '100'); Temporarily increase the connection pool
capacity by adjusting the number of connections, and the connection pool cache
can be refreshed in this way
- * Upgrade to replace the connection pool to Hikari version
- * Initialize datasource failed: CAUSED BY:
GetConnectionTimeoutException: wait millis 5006, active 10, maxActive 0,
creating 1
- * Reason 1: Network failure
- * Reason 2: The network latency is high, causing the connection
creation to take more than 5s
- * Solution
- * Check network
- * alter catalog <catalog_name> set properties
('connection_pool_max_wait' = '10000'); Increase the timeout
-* HikariCP connection pool version
- * HikariPool-2 - Connection is not available, request timed out after
5000ms
- * Reason 1: Network failure
- * Reason 2: The network delay is high, causing the connection creation
to take more than 5s
- * Reason 3: Too many queries cause the number of connections to exceed
the configuration
- * Solution
- * Check network
- * alter catalog <catalog_name> set properties
('connection_pool_max_size' = '100'); Increase the number of connections
- * alter catalog <catalog_name> set properties
('connection_pool_max_wait_time' = '10000'); Increase the timeout
+## Troubleshooting connection pool issues
+
+### HikariPool Connection Timeout Error:
+
+`Connection is not available, request timed out after 5000ms`
+
+#### Possible Causes:
+- **Reason 1**: Network issue (e.g., unreachable server)
+- **Reason 2**: Authentication issues, such as invalid username or password
+- **Reason 3**: High network latency, causing connection creation to exceed
the 5-second timeout
+- **Reason 4**: Too many concurrent queries, exceeding the maximum connection
pool size
+
+#### Resolution Steps:
+- **If only the error "Connection is not available, request timed out after
5000ms" appears**, check for **Reason 3** and **Reason 4**:
+ - Check if there is high network latency or resource exhaustion.
+ - Increase the connection pool size:
+ ```sql
+ ALTER CATALOG <catalog_name> SET PROPERTIES ('connection_pool_max_size'
= '100');
+ ```
+ - Increase the connection timeout threshold:
+ ```sql
+ ALTER CATALOG <catalog_name> SET PROPERTIES
('connection_pool_max_wait_time' = '10000');
+ ```
+
+- **If there are other error messages besides "Connection is not available,
request timed out after 5000ms"**, consider checking for additional issues:
+ - **Network issues** (e.g. server unreachable) may cause connection
failure. Please check whether the network connection is normal.
+ - **Authentication issues** (e.g., invalid username/password) could also
cause connection failures. Check the database credentials used in the
configuration and ensure they are correct.
+ - Investigate specific errors for root causes related to network,
database, or authentication problems.
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/current/lakehouse/database/jdbc.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/current/lakehouse/database/jdbc.md
index 5a52f0ea06d..ae4d4bf1738 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/current/lakehouse/database/jdbc.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/current/lakehouse/database/jdbc.md
@@ -69,7 +69,7 @@ Doris JDBC Catalog 支持连接以下数据库：
| 参数 | 默认值 | 说明
|
|---------------------------------|---------|-----------------------------------------------------------------------------|
| `connection_pool_min_size` | 1 |
定义连接池的最小连接数，用于初始化连接池并保证在启用保活机制时至少有该数量的连接处于活跃状态。 |
-| `connection_pool_max_size` | 10 | 定义连接池的最大连接数，每个 Catalog 对应的每个 FE
或 BE 节点最多可持有此数量的连接。 |
+| `connection_pool_max_size` | 30 | 定义连接池的最大连接数，每个 Catalog 对应的每个 FE
或 BE 节点最多可持有此数量的连接。 |
| `connection_pool_max_wait_time` | 5000 | 如果连接池中没有可用连接，定义客户端等待连接的最大毫秒数。
|
| `connection_pool_max_life_time` | 1800000 |
设置连接在连接池中保持活跃的最大时长（毫秒）。超时的连接将被回收。同时，此值的一半将作为连接池的最小逐出空闲时间，达到该时间的连接将成为逐出候选对象。 |
| `connection_pool_keep_alive` | false | 仅在 BE
节点上有效，用于决定是否保持达到最小逐出空闲时间但未到最大生命周期的连接活跃。默认关闭，以减少不必要的资源使用。 |
@@ -321,29 +321,29 @@ select * from query("catalog" = "jdbc_catalog", "query" =
"select * from db_name
## 连接池问题排查
-1. 在小于 2.0.5 的版本，连接池相关配置只能在 BE conf 的 JAVA_OPTS 中配置，参考 2.0.4 版本的
[be.conf](https://github.com/apache/doris/blob/2.0.4-rc06/conf/be.conf#L22)。
-2. 在 2.0.5 及之后的版本，连接池相关配置可以在 Catalog 属性中配置，参考 [连接池属性](#连接池属性)。
-3. Doris 使用的连接池在 2.0.10（2.0 Release）和 2.1.3（2.1 Release）开始从 Druid 换为
HikariCP，故连接池相关报错以及原因排查方式有所不同，参考如下
-
-* Druid 连接池版本
- * Initialize datasource failed: CAUSED BY: GetConnectionTimeoutException:
wait millis 5006, active 10, maxActive 10, creating 1
- * 原因 1：查询太多导致连接个数超出配置
- * 原因 2：连接池计数异常导致活跃计数未下降
- * 解决方法
- * alter catalog <catalog_name> set properties
('connection_pool_max_size' = '100'); 暂时通过调整连接数来增大连接池容量，且可以通过这种方式刷新连接池缓存
- * 升级到更换连接池到 Hikari 版本
- * Initialize datasource failed: CAUSED BY:
GetConnectionTimeoutException: wait millis 5006, active 10, maxActive 0,
creating 1
- * 原因 1：网络不通
- * 原因 2：网络延迟高，导致创建连接超过 5s
- * 解决方法
- * 检查网络
- * alter catalog <catalog_name> set properties
('connection_pool_max_wait' = '10000'); 调大超时时间
-* HikariCP 连接池版本
- * HikariPool-2 - Connection is not available, request timed out after
5000ms
- * 原因 1：网络不通
- * 原因 2：网络延迟高，导致创建连接超过 5s
- * 原因 3：查询太多导致连接个数超出配置
- * 解决方法
- * 检查网络
- * alter catalog <catalog_name> set properties
('connection_pool_max_size' = '100'); 调大连接个数
- * alter catalog <catalog_name> set properties
('connection_pool_max_wait_time' = '10000'); 调大超时时间
+### HikariPool 获取连接超时错误
+
+`Connection is not available, request timed out after 5000ms`
+
+#### 可能的原因：
+- **原因 1**：网络问题（例如，服务器不可达）
+- **原因 2**：身份认证问题，例如无效的用户名或密码
+- **原因 3**：网络延迟过高，导致创建连接超过 5 秒超时时间
+- **原因 4**：并发查询过多，超过了连接池配置的最大连接数
+
+#### 解决方案：
+- **如果只有 "Connection is not available, request timed out after 5000ms"
这一类错误**，请检查 **原因 3** 和 **原因 4**：
+ - 检查是否存在网络延迟过高或资源耗尽的情况。
+ - 调大连接池的最大连接数：
+ ```sql
+ ALTER CATALOG <catalog_name> SET PROPERTIES ('connection_pool_max_size'
= '100');
+ ```
+ - 调大连接超时时间：
+ ```sql
+ ALTER CATALOG <catalog_name> SET PROPERTIES
('connection_pool_max_wait_time' = '10000');
+ ```
+
+- **如果除了 "Connection is not available, request timed out after 5000ms"
之外还有其他错误信息**，请检查这些附加错误：
+ - **网络问题**（例如，服务器不可达）可能导致连接失败。请检查网络连接是否正常。
+ - **身份认证问题**（例如，用户名或密码无效）也可能导致连接失败。请检查配置中使用的数据库凭据，确保用户名和密码正确无误。
+ - 根据具体错误信息，调查与网络、数据库或身份认证相关的问题，找出根本原因。
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.0/lakehouse/database/jdbc.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.0/lakehouse/database/jdbc.md
index 06edaaf4065..92d3d7dba9b 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.0/lakehouse/database/jdbc.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.0/lakehouse/database/jdbc.md
@@ -67,7 +67,7 @@ Doris JDBC Catalog 支持连接以下数据库：
| 参数 | 默认值 | 说明 |
|---------------------------------|---------|-------------------------------|
| `connection_pool_min_size` | 1 |
定义连接池的最小连接数，用于初始化连接池并保证在启用保活机制时至少有该数量的连接处于活跃状态。 |
-| `connection_pool_max_size` | 10 | 定义连接池的最大连接数，每个 Catalog 对应的每个 FE
或 BE 节点最多可持有此数量的连接。 |
+| `connection_pool_max_size` | 30 | 定义连接池的最大连接数，每个 Catalog 对应的每个 FE
或 BE 节点最多可持有此数量的连接。 |
| `connection_pool_max_wait_time` | 5000 | 如果连接池中没有可用连接，定义客户端等待连接的最大毫秒数。
|
| `connection_pool_max_life_time` | 1800000 |
设置连接在连接池中保持活跃的最大时长（毫秒）。超时的连接将被回收。同时，此值的一半将作为连接池的最小逐出空闲时间，达到该时间的连接将成为逐出候选对象。 |
| `connection_pool_keep_alive` | false | 仅在 BE
节点上有效，用于决定是否保持达到最小逐出空闲时间但未到最大生命周期的连接活跃。默认关闭，以减少不必要的资源使用。 |
@@ -219,25 +219,44 @@ SELECT * FROM mysql.test.table;
2. 在 2.0.5 及之后的版本，连接池相关配置可以在 Catalog 属性中配置，参考 [连接池属性](#连接池属性)。
3. Doris 使用的连接池在 2.0.10（2.0 Release）和 2.1.3（2.1 Release）开始从 Druid 换为
HikariCP，故连接池相关报错以及原因排查方式有所不同，参考如下
-* Druid 连接池版本
- * Initialize datasource failed: CAUSED BY: GetConnectionTimeoutException:
wait millis 5006, active 10, maxActive 10, creating 1
- * 原因 1：查询太多导致连接个数超出配置
- * 原因 2：连接池计数异常导致活跃计数未下降
- * 解决方法
- * alter catalog <catalog_name> set properties
('connection_pool_max_size' = '100'); 暂时通过调整连接数来增大连接池容量，且可以通过这种方式刷新连接池缓存
- * 升级到更换连接池到 Hikari 版本
- * Initialize datasource failed: CAUSED BY: GetConnectionTimeoutException:
wait millis 5006, active 10, maxActive 0, creating 1
- * 原因 1：网络不通
- * 原因 2：网络延迟高，导致创建连接超过 5s
- * 解决方法
- * 检查网络
- * alter catalog <catalog_name> set properties
('connection_pool_max_wait' = '10000'); 调大超时时间
-* HikariCP 连接池版本
- * HikariPool-2 - Connection is not available, request timed out after 5000ms
- * 原因 1：网络不通
- * 原因 2：网络延迟高，导致创建连接超过 5s
- * 原因 3：查询太多导致连接个数超出配置
- * 解决方法
- * 检查网络
- * alter catalog <catalog_name> set properties
('connection_pool_max_size' = '100'); 调大连接个数
- * alter catalog <catalog_name> set properties
('connection_pool_max_wait_time' = '10000'); 调大超时时间
+### Druid 连接池版本
+**Initialize datasource failed: CAUSED BY: GetConnectionTimeoutException:
wait millis 5006, active 10, maxActive 10, creating 1**
+* 原因 1：查询太多导致连接个数超出配置
+* 原因 2：连接池计数异常导致活跃计数未下降
+* 解决方法
+ * alter catalog <catalog_name> set properties ('connection_pool_max_size'
= '100'); 暂时通过调整连接数来增大连接池容量，且可以通过这种方式刷新连接池缓存
+ * 升级到更换连接池到 Hikari 版本
+
+**Initialize datasource failed: CAUSED BY: GetConnectionTimeoutException:
wait millis 5006, active 10, maxActive 0, creating 1**
+* 原因 1：网络不通
+* 原因 2：网络延迟高，导致创建连接超过 5s
+* 解决方法
+ * 检查网络
+ * alter catalog <catalog_name> set properties ('connection_pool_max_wait'
= '10000'); 调大超时时间
+
+### HikariCP 连接池版本
+
+`Connection is not available, request timed out after 5000ms`
+
+#### 可能的原因：
+- **原因 1**：网络问题（例如，服务器不可达）
+- **原因 2**：身份认证问题，例如无效的用户名或密码
+- **原因 3**：网络延迟过高，导致创建连接超过 5 秒超时时间
+- **原因 4**：并发查询过多，超过了连接池配置的最大连接数
+
+#### 解决方案：
+- **如果只有 "Connection is not available, request timed out after 5000ms"
这一类错误**，请检查 **原因 3** 和 **原因 4**：
+ - 检查是否存在网络延迟过高或资源耗尽的情况。
+ - 调大连接池的最大连接数：
+ ```sql
+ ALTER CATALOG <catalog_name> SET PROPERTIES ('connection_pool_max_size'
= '100');
+ ```
+ - 调大连接超时时间：
+ ```sql
+ ALTER CATALOG <catalog_name> SET PROPERTIES
('connection_pool_max_wait_time' = '10000');
+ ```
+
+- **如果除了 "Connection is not available, request timed out after 5000ms"
之外还有其他错误信息**，请检查这些附加错误：
+ - **网络问题**（例如，服务器不可达）可能导致连接失败。请检查网络连接是否正常。
+ - **身份认证问题**（例如，用户名或密码无效）也可能导致连接失败。请检查配置中使用的数据库凭据，确保用户名和密码正确无误。
+ - 根据具体错误信息，调查与网络、数据库或身份认证相关的问题，找出根本原因。
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/lakehouse/database/jdbc.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/lakehouse/database/jdbc.md
index 865c22f53af..a350d38eea8 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/lakehouse/database/jdbc.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/lakehouse/database/jdbc.md
@@ -69,7 +69,7 @@ Doris JDBC Catalog 支持连接以下数据库：
| 参数 | 默认值 | 说明
|
|---------------------------------|---------|---------------------------------------------------|
| `connection_pool_min_size` | 1 |
定义连接池的最小连接数，用于初始化连接池并保证在启用保活机制时至少有该数量的连接处于活跃状态。 |
-| `connection_pool_max_size` | 10 | 定义连接池的最大连接数，每个 Catalog 对应的每个 FE
或 BE 节点最多可持有此数量的连接。 |
+| `connection_pool_max_size` | 30 | 定义连接池的最大连接数，每个 Catalog 对应的每个 FE
或 BE 节点最多可持有此数量的连接。 |
| `connection_pool_max_wait_time` | 5000 | 如果连接池中没有可用连接，定义客户端等待连接的最大毫秒数。 |
| `connection_pool_max_life_time` | 1800000 |
设置连接在连接池中保持活跃的最大时长（毫秒）。超时的连接将被回收。同时，此值的一半将作为连接池的最小逐出空闲时间，达到该时间的连接将成为逐出候选对象。 |
| `connection_pool_keep_alive` | false | 仅在 BE
节点上有效，用于决定是否保持达到最小逐出空闲时间但未到最大生命周期的连接活跃。默认关闭，以减少不必要的资源使用。 |
@@ -340,11 +340,27 @@ select * from query("catalog" = "jdbc_catalog", "query" =
"select * from db_name
### HikariCP 连接池版本
-**HikariPool-2 - Connection is not available, request timed out after 5000ms**
-* 原因 1：网络不通
-* 原因 2：网络延迟高，导致创建连接超过 5s
-* 原因 3：查询太多导致连接个数超出配置
-* 解决方法
- * 检查网络
- * alter catalog <catalog_name> set properties ('connection_pool_max_size'
= '100'); 调大连接个数
- * alter catalog <catalog_name> set properties
('connection_pool_max_wait_time' = '10000'); 调大超时时间
+`Connection is not available, request timed out after 5000ms`
+
+#### 可能的原因：
+- **原因 1**：网络问题（例如，服务器不可达）
+- **原因 2**：身份认证问题，例如无效的用户名或密码
+- **原因 3**：网络延迟过高，导致创建连接超过 5 秒超时时间
+- **原因 4**：并发查询过多，超过了连接池配置的最大连接数
+
+#### 解决方案：
+- **如果只有 "Connection is not available, request timed out after 5000ms"
这一类错误**，请检查 **原因 3** 和 **原因 4**：
+ - 检查是否存在网络延迟过高或资源耗尽的情况。
+ - 调大连接池的最大连接数：
+ ```sql
+ ALTER CATALOG <catalog_name> SET PROPERTIES ('connection_pool_max_size'
= '100');
+ ```
+ - 调大连接超时时间：
+ ```sql
+ ALTER CATALOG <catalog_name> SET PROPERTIES
('connection_pool_max_wait_time' = '10000');
+ ```
+
+- **如果除了 "Connection is not available, request timed out after 5000ms"
之外还有其他错误信息**，请检查这些附加错误：
+ - **网络问题**（例如，服务器不可达）可能导致连接失败。请检查网络连接是否正常。
+ - **身份认证问题**（例如，用户名或密码无效）也可能导致连接失败。请检查配置中使用的数据库凭据，确保用户名和密码正确无误。
+ - 根据具体错误信息，调查与网络、数据库或身份认证相关的问题，找出根本原因。
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.0/lakehouse/database/jdbc.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.0/lakehouse/database/jdbc.md
index 23bb0f06343..12dc19d50fc 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.0/lakehouse/database/jdbc.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.0/lakehouse/database/jdbc.md
@@ -69,7 +69,7 @@ Doris JDBC Catalog 支持连接以下数据库：
| 参数 | 默认值 | 说明
|
|---------------------------------|---------|----------------------------------------|
| `connection_pool_min_size` | 1 |
定义连接池的最小连接数，用于初始化连接池并保证在启用保活机制时至少有该数量的连接处于活跃状态。 |
-| `connection_pool_max_size` | 10 | 定义连接池的最大连接数，每个 Catalog 对应的每个 FE
或 BE 节点最多可持有此数量的连接。 |
+| `connection_pool_max_size` | 30 | 定义连接池的最大连接数，每个 Catalog 对应的每个 FE
或 BE 节点最多可持有此数量的连接。 |
| `connection_pool_max_wait_time` | 5000 | 如果连接池中没有可用连接，定义客户端等待连接的最大毫秒数。
|
| `connection_pool_max_life_time` | 1800000 |
设置连接在连接池中保持活跃的最大时长（毫秒）。超时的连接将被回收。同时，此值的一半将作为连接池的最小逐出空闲时间，达到该时间的连接将成为逐出候选对象。 |
| `connection_pool_keep_alive` | false | 仅在 BE
节点上有效，用于决定是否保持达到最小逐出空闲时间但未到最大生命周期的连接活跃。默认关闭，以减少不必要的资源使用。 |
@@ -319,33 +319,29 @@ select * from query("catalog" = "jdbc_catalog", "query" =
"select * from db_name
## 连接池问题排查
-1. 在小于 2.0.5 的版本，连接池相关配置只能在 BE conf 的 JAVA_OPTS 中配置，参考 2.0.4 版本的
[be.conf](https://github.com/apache/doris/blob/2.0.4-rc06/conf/be.conf#L22)。
-2. 在 2.0.5 及之后的版本，连接池相关配置可以在 Catalog 属性中配置，参考 [连接池属性](#连接池属性)。
-3. Doris 使用的连接池在 2.0.10（2.0 Release）和 2.1.3（2.1 Release）开始从 Druid 换为
HikariCP，故连接池相关报错以及原因排查方式有所不同，参考如下
-
-### Druid 连接池版本
-
-**Initialize datasource failed: CAUSED BY: GetConnectionTimeoutException:
wait millis 5006, active 10, maxActive 10, creating 1**
-* 原因 1：查询太多导致连接个数超出配置
-* 原因 2：连接池计数异常导致活跃计数未下降
-* 解决方法
- * alter catalog <catalog_name> set properties ('connection_pool_max_size' =
'100'); 暂时通过调整连接数来增大连接池容量，且可以通过这种方式刷新连接池缓存
- * 升级到更换连接池到 Hikari 版本
-
-**Initialize datasource failed: CAUSED BY: GetConnectionTimeoutException:
wait millis 5006, active 10, maxActive 0, creating 1**
-* 原因 1：网络不通
-* 原因 2：网络延迟高，导致创建连接超过 5s
-* 解决方法
- * 检查网络
- * alter catalog <catalog_name> set properties ('connection_pool_max_wait' =
'10000'); 调大超时时间
-
-### HikariCP 连接池版本
-
-**HikariPool-2 - Connection is not available, request timed out after 5000ms**
-* 原因 1：网络不通
-* 原因 2：网络延迟高，导致创建连接超过 5s
-* 原因 3：查询太多导致连接个数超出配置
-* 解决方法
- * 检查网络
- * alter catalog <catalog_name> set properties ('connection_pool_max_size' =
'100'); 调大连接个数
- * alter catalog <catalog_name> set properties
('connection_pool_max_wait_time' = '10000'); 调大超时时间
+### HikariPool 获取连接超时错误
+
+`Connection is not available, request timed out after 5000ms`
+
+#### 可能的原因：
+- **原因 1**：网络问题（例如，服务器不可达）
+- **原因 2**：身份认证问题，例如无效的用户名或密码
+- **原因 3**：网络延迟过高，导致创建连接超过 5 秒超时时间
+- **原因 4**：并发查询过多，超过了连接池配置的最大连接数
+
+#### 解决方案：
+- **如果只有 "Connection is not available, request timed out after 5000ms"
这一类错误**，请检查 **原因 3** 和 **原因 4**：
+ - 检查是否存在网络延迟过高或资源耗尽的情况。
+ - 调大连接池的最大连接数：
+ ```sql
+ ALTER CATALOG <catalog_name> SET PROPERTIES ('connection_pool_max_size'
= '100');
+ ```
+ - 调大连接超时时间：
+ ```sql
+ ALTER CATALOG <catalog_name> SET PROPERTIES
('connection_pool_max_wait_time' = '10000');
+ ```
+
+- **如果除了 "Connection is not available, request timed out after 5000ms"
之外还有其他错误信息**，请检查这些附加错误：
+ - **网络问题**（例如，服务器不可达）可能导致连接失败。请检查网络连接是否正常。
+ - **身份认证问题**（例如，用户名或密码无效）也可能导致连接失败。请检查配置中使用的数据库凭据，确保用户名和密码正确无误。
+ - 根据具体错误信息，调查与网络、数据库或身份认证相关的问题，找出根本原因。
diff --git a/versioned_docs/version-2.0/lakehouse/database/jdbc.md
b/versioned_docs/version-2.0/lakehouse/database/jdbc.md
index 640e95938c5..01b8f50919e 100644
--- a/versioned_docs/version-2.0/lakehouse/database/jdbc.md
+++ b/versioned_docs/version-2.0/lakehouse/database/jdbc.md
@@ -67,7 +67,7 @@ Doris JDBC Catalog supports connecting to the following
databases:
| Parameter | Default value | Description
|
|---------------------------------|----------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| `connection_pool_min_size` | 1 | Defines the minimum
number of connections in the connection pool, which is used to initialize the
connection pool and ensure that at least this number of connections are active
when the keep-alive mechanism is enabled.
|
-| `connection_pool_max_size` | 10 | Defines the maximum
number of connections in the connection pool. Each FE or BE node corresponding
to each Catalog can hold up to this number of connections.
|
+| `connection_pool_max_size` | 30 | Defines the maximum
number of connections in the connection pool. Each FE or BE node corresponding
to each Catalog can hold up to this number of connections.
|
| `connection_pool_max_wait_time` | 5000 | Defines the maximum
number of milliseconds the client will wait for a connection if there is no
available connection in the connection pool.
|
| `connection_pool_max_life_time` | 1800000 | Set the maximum time (in
milliseconds) that a connection remains active in the connection pool. Timed
out connections will be recycled. At the same time, half of this value will
serve as the minimum eviction idle time of the connection pool, and connections
that reach this time will become eviction candidates. |
| `connection_pool_keep_alive` | false | Only valid on BE nodes,
used to decide whether to keep connections that have reached the minimum
eviction idle time but have not reached the maximum lifetime active. Turned off
by default to reduce unnecessary resource usage.
|
@@ -272,25 +272,44 @@ Through the `CALL EXECUTE_STMT()` command, Doris will
directly send the SQL stat
2. In versions 2.0.5 and later, connection pool related configurations can be
configured in the Catalog properties, refer to [Connection Pool
Properties](#Connection Pool Properties).
3. The connection pool used by Doris was changed from Druid to HikariCP
starting from 2.0.10 (2.0 Release) and 2.1.3 (2.1 Release), so the connection
pool related errors and troubleshooting methods are different, refer to the
following
-* Druid connection pool version
- * Initialize datasource failed: CAUSED BY: GetConnectionTimeoutException:
wait millis 5006, active 10, maxActive 10, creating 1
- * Reason 1: Too many queries cause the number of connections to exceed
the configuration
- * Reason 2: The connection pool count is abnormal and the active count
does not decrease.
- * Solution
- * alter catalog <catalog_name> set properties
('connection_pool_max_size' = '100'); Temporarily increase the connection pool
capacity by adjusting the number of connections, and the connection pool cache
can be refreshed in this way
- * Upgrade to replace the connection pool to Hikari version
- * Initialize datasource failed: CAUSED BY:
GetConnectionTimeoutException: wait millis 5006, active 10, maxActive 0,
creating 1
- * Reason 1: Network failure
- * Reason 2: The network latency is high, causing the connection
creation to take more than 5s
- * Solution
- * Check network
- * alter catalog <catalog_name> set properties
('connection_pool_max_wait' = '10000'); Increase the timeout
-* HikariCP connection pool version
- * HikariPool-2 - Connection is not available, request timed out after 5000ms
- * Reason 1: Network failure
- * Reason 2: The network delay is high, causing the connection creation
to take more than 5s
- * Reason 3: Too many queries cause the number of connections to exceed
the configuration
- * Solution
- * Check network
- * alter catalog <catalog_name> set properties
('connection_pool_max_size' = '100'); Increase the number of connections
- * alter catalog <catalog_name> set properties
('connection_pool_max_wait_time' = '10000'); Increase the timeout
+### Druid connection pool version
+**Initialize datasource failed: CAUSED BY: GetConnectionTimeoutException: wait
millis 5006, active 10, maxActive 10, creating 1**
+* Reason 1: Too many queries cause the number of connections to exceed the
configuration
+* Reason 2: The connection pool count is abnormal and the active count does
not decrease.
+* Solution
+ * alter catalog <catalog_name> set properties ('connection_pool_max_size' =
'100'); Temporarily increase the connection pool capacity by adjusting the
number of connections, and the connection pool cache can be refreshed in this
way
+ * Upgrade to replace the connection pool to Hikari version
+
+**Initialize datasource failed: CAUSED BY: GetConnectionTimeoutException: wait
millis 5006, active 10, maxActive 0, creating 1**
+* Reason 1: Network failure
+* Reason 2: The network delay is high, causing the connection creation to take
more than 5s
+* Solution
+ * Check network
+ * alter catalog <catalog_name> set properties ('connection_pool_max_wait' =
'10000'); Increase the timeout
+
+### HikariCP connection pool version
+
+`Connection is not available, request timed out after 5000ms`
+
+#### Possible reasons:
+- **Cause 1**: Network problem (e.g. server unreachable)
+- **Cause 2**: Authentication issues, such as invalid username or password
+- **Cause 3**: The network latency is too high, causing the connection
creation to exceed the 5 second timeout
+- **Cause 4**: Too many concurrent queries, exceeding the maximum number of
connections configured in the connection pool
+
+#### Solution:
+- **If there are only "Connection is not available, request timed out after
5000ms" errors**, please check **Cause 3** and **Cause 4**:
+ - Check for high network latency or resource exhaustion.
+ - Increase the maximum number of connections in the connection pool:
+ ```sql
+ ALTER CATALOG <catalog_name> SET PROPERTIES ('connection_pool_max_size' =
'100');
+ ```
+ - Increase the connection timeout:
+ ```sql
+ ALTER CATALOG <catalog_name> SET PROPERTIES
('connection_pool_max_wait_time' = '10000');
+ ```
+
+- **If there are other error messages besides "Connection is not available,
request timed out after 5000ms"**, please check these additional errors:
+ - **Network problems** (e.g. server unreachable) may cause connection
failure. Please check whether the network connection is normal.
+ - **Authentication issues** (e.g. invalid username or password) may also
cause connection failure. Please check the database credentials used in the
configuration to ensure that the username and password are correct.
+ - Based on specific error messages, investigate network, database, or
authentication-related issues to identify the root cause.
diff --git a/versioned_docs/version-2.1/lakehouse/database/jdbc.md
b/versioned_docs/version-2.1/lakehouse/database/jdbc.md
index 803a468bf57..28f66ae4da0 100644
--- a/versioned_docs/version-2.1/lakehouse/database/jdbc.md
+++ b/versioned_docs/version-2.1/lakehouse/database/jdbc.md
@@ -69,7 +69,7 @@ Doris JDBC Catalog supports connecting to the following
databases:
| Parameter | Default value | Description
|
|---------------------------------|----------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| `connection_pool_min_size` | 1 | Defines the minimum
number of connections in the connection pool, which is used to initialize the
connection pool and ensure that at least this number of connections are active
when the keep-alive mechanism is enabled.
|
-| `connection_pool_max_size` | 10 | Defines the maximum
number of connections in the connection pool. Each FE or BE node corresponding
to each Catalog can hold up to this number of connections.
|
+| `connection_pool_max_size` | 30 | Defines the maximum
number of connections in the connection pool. Each FE or BE node corresponding
to each Catalog can hold up to this number of connections.
|
| `connection_pool_max_wait_time` | 5000 | Defines the maximum
number of milliseconds the client will wait for a connection if there is no
available connection in the connection pool.
|
| `connection_pool_max_life_time` | 1800000 | Set the maximum time (in
milliseconds) that a connection remains active in the connection pool. Timed
out connections will be recycled. At the same time, half of this value will
serve as the minimum eviction idle time of the connection pool, and connections
that reach this time will become eviction candidates. |
| `connection_pool_keep_alive` | false | Only valid on BE nodes,
used to decide whether to keep connections that have reached the minimum
eviction idle time but have not reached the maximum lifetime active. Turned off
by default to reduce unnecessary resource usage.
|
@@ -323,25 +323,44 @@ Through the `CALL EXECUTE_STMT()` command, Doris will
directly send the SQL stat
2. In versions 2.0.5 and later, connection pool related configurations can be
configured in the Catalog properties, refer to [Connection Pool
Properties](#Connection Pool Properties).
3. The connection pool used by Doris was changed from Druid to HikariCP
starting from 2.0.10 (2.0 Release) and 2.1.3 (2.1 Release), so the connection
pool related errors and troubleshooting methods are different, refer to the
following
-* Druid connection pool version
- * Initialize datasource failed: CAUSED BY: GetConnectionTimeoutException:
wait millis 5006, active 10, maxActive 10, creating 1
- * Reason 1: Too many queries cause the number of connections to exceed
the configuration
- * Reason 2: The connection pool count is abnormal and the active count
does not decrease.
- * Solution
- * alter catalog <catalog_name> set properties
('connection_pool_max_size' = '100'); Temporarily increase the connection pool
capacity by adjusting the number of connections, and the connection pool cache
can be refreshed in this way
- * Upgrade to replace the connection pool to Hikari version
- * Initialize datasource failed: CAUSED BY:
GetConnectionTimeoutException: wait millis 5006, active 10, maxActive 0,
creating 1
- * Reason 1: Network failure
- * Reason 2: The network latency is high, causing the connection
creation to take more than 5s
- * Solution
- * Check network
- * alter catalog <catalog_name> set properties
('connection_pool_max_wait' = '10000'); Increase the timeout
-* HikariCP connection pool version
- * HikariPool-2 - Connection is not available, request timed out after
5000ms
- * Reason 1: Network failure
- * Reason 2: The network delay is high, causing the connection creation
to take more than 5s
- * Reason 3: Too many queries cause the number of connections to exceed
the configuration
- * Solution
- * Check network
- * alter catalog <catalog_name> set properties
('connection_pool_max_size' = '100'); Increase the number of connections
- * alter catalog <catalog_name> set properties
('connection_pool_max_wait_time' = '10000'); Increase the timeout
+### Druid connection pool version
+**Initialize datasource failed: CAUSED BY: GetConnectionTimeoutException: wait
millis 5006, active 10, maxActive 10, creating 1**
+* Reason 1: Too many queries cause the number of connections to exceed the
configuration
+* Reason 2: The connection pool count is abnormal and the active count does
not decrease.
+* Solution
+ * alter catalog <catalog_name> set properties ('connection_pool_max_size'
= '100'); Temporarily increase the connection pool capacity by adjusting the
number of connections, and the connection pool cache can be refreshed in this
way
+ * Upgrade to replace the connection pool to Hikari version
+
+**Initialize datasource failed: CAUSED BY: GetConnectionTimeoutException: wait
millis 5006, active 10, maxActive 0, creating 1**
+* Reason 1: Network failure
+* Reason 2: The network delay is high, causing the connection creation to take
more than 5s
+* Solution
+ * Check network
+ * alter catalog <catalog_name> set properties ('connection_pool_max_wait'
= '10000'); Increase the timeout
+
+### HikariCP connection pool version
+
+`Connection is not available, request timed out after 5000ms`
+
+#### Possible reasons:
+- **Cause 1**: Network problem (e.g. server unreachable)
+- **Cause 2**: Authentication issues, such as invalid username or password
+- **Cause 3**: The network latency is too high, causing the connection
creation to exceed the 5 second timeout
+- **Cause 4**: Too many concurrent queries, exceeding the maximum number of
connections configured in the connection pool
+
+#### Solution:
+- **If there are only "Connection is not available, request timed out after
5000ms" errors**, please check **Cause 3** and **Cause 4**:
+ - Check for high network latency or resource exhaustion.
+ - Increase the maximum number of connections in the connection pool:
+ ```sql
+ ALTER CATALOG <catalog_name> SET PROPERTIES ('connection_pool_max_size'
= '100');
+ ```
+ - Increase the connection timeout:
+ ```sql
+ ALTER CATALOG <catalog_name> SET PROPERTIES
('connection_pool_max_wait_time' = '10000');
+ ```
+
+- **If there are other error messages besides "Connection is not available,
request timed out after 5000ms"**, please check these additional errors:
+ - **Network problems** (e.g. server unreachable) may cause connection
failure. Please check whether the network connection is normal.
+ - **Authentication issues** (e.g. invalid username or password) may also
cause connection failure. Please check the database credentials used in the
configuration to ensure that the username and password are correct.
+ - Based on specific error messages, investigate network, database, or
authentication-related issues to identify the root cause.
diff --git a/versioned_docs/version-3.0/lakehouse/database/jdbc.md
b/versioned_docs/version-3.0/lakehouse/database/jdbc.md
index 803a468bf57..d8ecf246273 100644
--- a/versioned_docs/version-3.0/lakehouse/database/jdbc.md
+++ b/versioned_docs/version-3.0/lakehouse/database/jdbc.md
@@ -69,7 +69,7 @@ Doris JDBC Catalog supports connecting to the following
databases:
| Parameter | Default value | Description
|
|---------------------------------|----------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| `connection_pool_min_size` | 1 | Defines the minimum
number of connections in the connection pool, which is used to initialize the
connection pool and ensure that at least this number of connections are active
when the keep-alive mechanism is enabled.
|
-| `connection_pool_max_size` | 10 | Defines the maximum
number of connections in the connection pool. Each FE or BE node corresponding
to each Catalog can hold up to this number of connections.
|
+| `connection_pool_max_size` | 30 | Defines the maximum
number of connections in the connection pool. Each FE or BE node corresponding
to each Catalog can hold up to this number of connections.
|
| `connection_pool_max_wait_time` | 5000 | Defines the maximum
number of milliseconds the client will wait for a connection if there is no
available connection in the connection pool.
|
| `connection_pool_max_life_time` | 1800000 | Set the maximum time (in
milliseconds) that a connection remains active in the connection pool. Timed
out connections will be recycled. At the same time, half of this value will
serve as the minimum eviction idle time of the connection pool, and connections
that reach this time will become eviction candidates. |
| `connection_pool_keep_alive` | false | Only valid on BE nodes,
used to decide whether to keep connections that have reached the minimum
eviction idle time but have not reached the maximum lifetime active. Turned off
by default to reduce unnecessary resource usage.
|
@@ -319,29 +319,29 @@ Through the `CALL EXECUTE_STMT()` command, Doris will
directly send the SQL stat
## Troubleshooting connection pool issues
-1. In versions less than 2.0.5, the connection pool related configuration can
only be configured in JAVA_OPTS of BE conf, refer to version 2.0.4
[be.conf](https://github.com/apache/doris/blob/ 2.0.4-rc06/conf/be.conf#L22).
-2. In versions 2.0.5 and later, connection pool related configurations can be
configured in the Catalog properties, refer to [Connection Pool
Properties](#Connection Pool Properties).
-3. The connection pool used by Doris was changed from Druid to HikariCP
starting from 2.0.10 (2.0 Release) and 2.1.3 (2.1 Release), so the connection
pool related errors and troubleshooting methods are different, refer to the
following
-
-* Druid connection pool version
- * Initialize datasource failed: CAUSED BY: GetConnectionTimeoutException:
wait millis 5006, active 10, maxActive 10, creating 1
- * Reason 1: Too many queries cause the number of connections to exceed
the configuration
- * Reason 2: The connection pool count is abnormal and the active count
does not decrease.
- * Solution
- * alter catalog <catalog_name> set properties
('connection_pool_max_size' = '100'); Temporarily increase the connection pool
capacity by adjusting the number of connections, and the connection pool cache
can be refreshed in this way
- * Upgrade to replace the connection pool to Hikari version
- * Initialize datasource failed: CAUSED BY:
GetConnectionTimeoutException: wait millis 5006, active 10, maxActive 0,
creating 1
- * Reason 1: Network failure
- * Reason 2: The network latency is high, causing the connection
creation to take more than 5s
- * Solution
- * Check network
- * alter catalog <catalog_name> set properties
('connection_pool_max_wait' = '10000'); Increase the timeout
-* HikariCP connection pool version
- * HikariPool-2 - Connection is not available, request timed out after
5000ms
- * Reason 1: Network failure
- * Reason 2: The network delay is high, causing the connection creation
to take more than 5s
- * Reason 3: Too many queries cause the number of connections to exceed
the configuration
- * Solution
- * Check network
- * alter catalog <catalog_name> set properties
('connection_pool_max_size' = '100'); Increase the number of connections
- * alter catalog <catalog_name> set properties
('connection_pool_max_wait_time' = '10000'); Increase the timeout
+### HikariPool Connection Timeout Error:
+
+`Connection is not available, request timed out after 5000ms`
+
+#### Possible Causes:
+- **Reason 1**: Network issue (e.g., unreachable server)
+- **Reason 2**: Authentication issues, such as invalid username or password
+- **Reason 3**: High network latency, causing connection creation to exceed
the 5-second timeout
+- **Reason 4**: Too many concurrent queries, exceeding the maximum connection
pool size
+
+#### Resolution Steps:
+- **If only the error "Connection is not available, request timed out after
5000ms" appears**, check for **Reason 3** and **Reason 4**:
+ - Check if there is high network latency or resource exhaustion.
+ - Increase the connection pool size:
+ ```sql
+ ALTER CATALOG <catalog_name> SET PROPERTIES ('connection_pool_max_size'
= '100');
+ ```
+ - Increase the connection timeout threshold:
+ ```sql
+ ALTER CATALOG <catalog_name> SET PROPERTIES
('connection_pool_max_wait_time' = '10000');
+ ```
+
+- **If there are other error messages besides "Connection is not available,
request timed out after 5000ms"**, consider checking for additional issues:
+ - **Network issues** (e.g. server unreachable) may cause connection
failure. Please check whether the network connection is normal.
+ - **Authentication issues** (e.g., invalid username/password) could also
cause connection failures. Check the database credentials used in the
configuration and ensure they are correct.
+ - Investigate specific errors for root causes related to network,
database, or authentication problems.
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@doris.apache.org
For additional commands, e-mail: commits-h...@doris.apache.org
