This is an automated email from the ASF dual-hosted git repository.
morningman 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 bddeb0ecad4 [Kerberos]Add KerberosConnectivity Testing Tool (#3283)
bddeb0ecad4 is described below
commit bddeb0ecad4dde834a2189fcff8c02ef744459b4
Author: Calvin Kirs <[email protected]>
AuthorDate: Tue Jan 27 15:09:29 2026 +0800
[Kerberos]Add KerberosConnectivity Testing Tool (#3283)
---
docs/lakehouse/best-practices/kerberos.md | 11 +++++++++++
.../current/lakehouse/best-practices/kerberos.md | 7 +++++++
.../version-3.x/lakehouse/best-practices/kerberos.md | 6 ++++++
.../version-4.x/lakehouse/best-practices/kerberos.md | 6 ++++++
.../version-3.x/lakehouse/best-practices/kerberos.md | 10 ++++++++++
.../version-4.x/lakehouse/best-practices/kerberos.md | 10 ++++++++++
6 files changed, 50 insertions(+)
diff --git a/docs/lakehouse/best-practices/kerberos.md
b/docs/lakehouse/best-practices/kerberos.md
index 093571befd5..e6a32cb6de7 100644
--- a/docs/lakehouse/best-practices/kerberos.md
+++ b/docs/lakehouse/best-practices/kerberos.md
@@ -263,6 +263,17 @@ Or directly use 127.0.0.1 (provided that the service has
been mapped to the host
```
At this point, the multi-Kerberos cluster access configuration is complete.
You can view data from both Hive clusters and use different Kerberos
credentials.
+## Connectivity Testing Tool
+
+For verifying connectivity to external dependencies such as Kerberos,
+the open-source tool **Pulse** can be used.
+
+**Pulse is an independent open-source connectivity testing tool.
+For usage instructions, installation details, and release information,
+please refer to the project documentation.**
+
+- Documentation: [Kerberos Connectivity
Tool](https://github.com/CalvinKirs/Pulse/tree/main/kerberos-tools)
+- Release package: [Kerberos Connectivity Tool
v1.0.0](https://github.com/CalvinKirs/Pulse/releases/tag/v1.0.0)
## FAQ
1. javax.security.sasl.SaslException: No common protection layer between
client and server
- Cause: The client's `hadoop.rpc.protection` differs from the HDFS cluster
setting.
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/current/lakehouse/best-practices/kerberos.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/current/lakehouse/best-practices/kerberos.md
index e0406280722..bc516ebb612 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/current/lakehouse/best-practices/kerberos.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/current/lakehouse/best-practices/kerberos.md
@@ -263,6 +263,13 @@ docker inspect <container-name> | grep IPAddress
```
至此，完成多 Kerberos 集群访问配置，您可以查看两个 Hive 集群中的数据，并使用不同的 Kerberos 凭证。
+## 联通性检测工具
+对于 Kerberos 等外部依赖的联通性检查，可使用开源工具 **Pulse** 进行验证。
+
+**Pulse 是一个独立的开源联通性测试工具，相关使用方式、安装说明及版本发布，请参考其项目文档。**
+
+相关文档: [Kerberos Connectivity
Tool](https://github.com/CalvinKirs/Pulse/tree/main/kerberos-tools)
+安装包: [Kerberos Connectivity
Tool](https://github.com/CalvinKirs/Pulse/releases/tag/v1.0.0)
## FAQ
1. javax.security.sasl.SaslException: No common protection layer between
client and server
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/lakehouse/best-practices/kerberos.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/lakehouse/best-practices/kerberos.md
index 106230cd048..f4af03f04c4 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/lakehouse/best-practices/kerberos.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.x/lakehouse/best-practices/kerberos.md
@@ -263,7 +263,13 @@ docker inspect <container-name> | grep IPAddress
```
至此，完成多 Kerberos 集群访问配置，您可以查看两个 Hive 集群中的数据，并使用不同的 Kerberos 凭证。
+## 联通性检测工具
+对于 Kerberos 等外部依赖的联通性检查，可使用开源工具 **Pulse** 进行验证。
+**Pulse 是一个独立的开源联通性测试工具，相关使用方式、安装说明及版本发布，请参考其项目文档。**
+
+相关文档: [Kerberos Connectivity
Tool](https://github.com/CalvinKirs/Pulse/tree/main/kerberos-tools)
+安装包: [Kerberos Connectivity
Tool](https://github.com/CalvinKirs/Pulse/releases/tag/v1.0.0)
## FAQ
1. javax.security.sasl.SaslException: No common protection layer between
client and server
- 原因: 客户端的 hadoop.rpc.protection 配置与 HDFS 集群上的配置不一致。
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/lakehouse/best-practices/kerberos.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/lakehouse/best-practices/kerberos.md
index 106230cd048..f4af03f04c4 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/lakehouse/best-practices/kerberos.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/lakehouse/best-practices/kerberos.md
@@ -263,7 +263,13 @@ docker inspect <container-name> | grep IPAddress
```
至此，完成多 Kerberos 集群访问配置，您可以查看两个 Hive 集群中的数据，并使用不同的 Kerberos 凭证。
+## 联通性检测工具
+对于 Kerberos 等外部依赖的联通性检查，可使用开源工具 **Pulse** 进行验证。
+**Pulse 是一个独立的开源联通性测试工具，相关使用方式、安装说明及版本发布，请参考其项目文档。**
+
+相关文档: [Kerberos Connectivity
Tool](https://github.com/CalvinKirs/Pulse/tree/main/kerberos-tools)
+安装包: [Kerberos Connectivity
Tool](https://github.com/CalvinKirs/Pulse/releases/tag/v1.0.0)
## FAQ
1. javax.security.sasl.SaslException: No common protection layer between
client and server
- 原因: 客户端的 hadoop.rpc.protection 配置与 HDFS 集群上的配置不一致。
diff --git a/versioned_docs/version-3.x/lakehouse/best-practices/kerberos.md
b/versioned_docs/version-3.x/lakehouse/best-practices/kerberos.md
index 65bebefd859..94d196666c0 100644
--- a/versioned_docs/version-3.x/lakehouse/best-practices/kerberos.md
+++ b/versioned_docs/version-3.x/lakehouse/best-practices/kerberos.md
@@ -263,7 +263,17 @@ Or directly use 127.0.0.1 (provided that the service has
been mapped to the host
```
At this point, the multi-Kerberos cluster access configuration is complete.
You can view data from both Hive clusters and use different Kerberos
credentials.
+## Connectivity Testing Tool
+For verifying connectivity to external dependencies such as Kerberos,
+the open-source tool **Pulse** can be used.
+
+**Pulse is an independent open-source connectivity testing tool.
+For usage instructions, installation details, and release information,
+please refer to the project documentation.**
+
+- Documentation: [Kerberos Connectivity
Tool](https://github.com/CalvinKirs/Pulse/tree/main/kerberos-tools)
+- Release package: [Kerberos Connectivity Tool
v1.0.0](https://github.com/CalvinKirs/Pulse/releases/tag/v1.0.0)
## FAQ
1. javax.security.sasl.SaslException: No common protection layer between
client and server
- Cause: The client's `hadoop.rpc.protection` differs from the HDFS cluster
setting.
diff --git a/versioned_docs/version-4.x/lakehouse/best-practices/kerberos.md
b/versioned_docs/version-4.x/lakehouse/best-practices/kerberos.md
index 65bebefd859..94d196666c0 100644
--- a/versioned_docs/version-4.x/lakehouse/best-practices/kerberos.md
+++ b/versioned_docs/version-4.x/lakehouse/best-practices/kerberos.md
@@ -263,7 +263,17 @@ Or directly use 127.0.0.1 (provided that the service has
been mapped to the host
```
At this point, the multi-Kerberos cluster access configuration is complete.
You can view data from both Hive clusters and use different Kerberos
credentials.
+## Connectivity Testing Tool
+For verifying connectivity to external dependencies such as Kerberos,
+the open-source tool **Pulse** can be used.
+
+**Pulse is an independent open-source connectivity testing tool.
+For usage instructions, installation details, and release information,
+please refer to the project documentation.**
+
+- Documentation: [Kerberos Connectivity
Tool](https://github.com/CalvinKirs/Pulse/tree/main/kerberos-tools)
+- Release package: [Kerberos Connectivity Tool
v1.0.0](https://github.com/CalvinKirs/Pulse/releases/tag/v1.0.0)
## FAQ
1. javax.security.sasl.SaslException: No common protection layer between
client and server
- Cause: The client's `hadoop.rpc.protection` differs from the HDFS cluster
setting.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
