This is an automated email from the ASF dual-hosted git repository.
critas pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/iotdb-docs.git
The following commit(s) were added to refs/heads/main by this push:
new ce1a1d53 Change port number for cross gateway transmission (#673)
ce1a1d53 is described below
commit ce1a1d53feb932421306955f042b54761b615599
Author: W1y1r <[email protected]>
AuthorDate: Fri Mar 28 11:51:22 2025 +0800
Change port number for cross gateway transmission (#673)
* Change port number for cross gateway transmission
* Supporting gateway models requires modification of description information
---
src/.vuepress/public/img/cross-network-gateway.png | Bin 0 -> 78101 bytes
.../Master/Table/User-Manual/Data-Sync_timecho.md | 16 +++++++++++++++-
.../Master/Tree/User-Manual/Data-Sync_timecho.md | 3 ++-
.../V1.3.x/User-Manual/Data-Sync-old_timecho.md | 2 +-
src/UserGuide/V1.3.x/User-Manual/Data-Sync_timecho.md | 3 ++-
src/UserGuide/dev-1.3/User-Manual/Data-Sync_timecho.md | 3 ++-
.../latest-Table/User-Manual/Data-Sync_timecho.md | 16 +++++++++++++++-
src/UserGuide/latest/User-Manual/Data-Sync_timecho.md | 3 ++-
.../Master/Table/User-Manual/Data-Sync_timecho.md | 3 ++-
.../Master/Tree/User-Manual/Data-Sync_timecho.md | 3 ++-
.../UserGuide/V1.2.x/User-Manual/Data-Sync_timecho.md | 2 +-
.../V1.3.x/User-Manual/Data-Sync-old_timecho.md | 2 +-
.../UserGuide/V1.3.x/User-Manual/Data-Sync_timecho.md | 3 ++-
.../UserGuide/dev-1.3/User-Manual/Data-Sync_timecho.md | 4 +++-
.../latest-Table/User-Manual/Data-Sync_timecho.md | 3 ++-
.../UserGuide/latest/User-Manual/Data-Sync_timecho.md | 3 ++-
16 files changed, 54 insertions(+), 15 deletions(-)
diff --git a/src/.vuepress/public/img/cross-network-gateway.png
b/src/.vuepress/public/img/cross-network-gateway.png
new file mode 100644
index 00000000..b07a2895
Binary files /dev/null and b/src/.vuepress/public/img/cross-network-gateway.png
differ
diff --git a/src/UserGuide/Master/Table/User-Manual/Data-Sync_timecho.md
b/src/UserGuide/Master/Table/User-Manual/Data-Sync_timecho.md
index cb83f253..ddd9dcd6 100644
--- a/src/UserGuide/Master/Table/User-Manual/Data-Sync_timecho.md
+++ b/src/UserGuide/Master/Table/User-Manual/Data-Sync_timecho.md
@@ -421,7 +421,7 @@ WITH SINK (
This example demonstrates synchronizing data from one IoTDB to another through
a unidirectional air gap. The data pipeline is shown below:
-
+
In this example, the `iotdb-air-gap-sink` plugin is used (currently supports
specific air gap models; contact Timecho team for details). After configuring
the air gap, execute the following statement on IoTDB A, where `node-urls` is
the URL of the DataNode service port on the target IoTDB.
@@ -434,6 +434,19 @@ WITH SINK (
'node-urls' = '10.53.53.53:9780' -- URL of the DataNode service port on the
target IoTDB
)
```
+**Notes: Currently supported gateway models**
+> For other models of network gateway devices, Please contact timechodb staff
to confirm compatibility.
+
+| Gateway Type | Model
| Return Packet Limit | Send Limit |
+| ---------------------- |
------------------------------------------------------------ |
------------------- | ---------------------- |
+| Forward Gate | NARI Syskeeper-2000 Forward Gate
| All 0 / All 1 bytes | No Limit |
+| Forward Gate | XJ Self-developed Diaphragm
| All 0 / All 1 bytes | No Limit |
+| Unknown | WISGAP | No Limit | No Limit |
+| Forward Gate | KEDONG StoneWall-2000 Network Security Isolation
Device | No Limit | No Limit |
+| Reverse Gate | NARI Syskeeper-2000 Reverse Direction
| All 0 / All 1 bytes | Meet E Language Format |
+| Unknown | DPtech ISG5000 | No Limit
| No Limit |
+| Unknown | GAP
+ XL—GAP | No Limit | No Limit |
### 3.7 Compressed Synchronization
@@ -450,6 +463,7 @@ WITH SINK (
)
```
+
### 3.8 Encrypted Synchronization
IoTDB supports SSL encryption during synchronization to securely transmit data
between IoTDB instances. By configuring SSL-related parameters such as the
certificate path (`ssl.trust-store-path`) and password (`ssl.trust-store-pwd`),
data can be protected by SSL encryption during synchronization.
diff --git a/src/UserGuide/Master/Tree/User-Manual/Data-Sync_timecho.md
b/src/UserGuide/Master/Tree/User-Manual/Data-Sync_timecho.md
index 4db26993..28098034 100644
--- a/src/UserGuide/Master/Tree/User-Manual/Data-Sync_timecho.md
+++ b/src/UserGuide/Master/Tree/User-Manual/Data-Sync_timecho.md
@@ -433,7 +433,7 @@ with sink (
This example is used to demonstrate the scenario where data from one IoTDB is
synchronized to another IoTDB through a unidirectional gateway, as shown in the
figure below:
-
+
In this example, the iotdb-air-gap-sink plugin in the sink task needs to be
used . After configuring the gateway, execute the following statement on A
IoTDB. Fill in the node-urls with the URL of the data service port of the
DataNode node on the target IoTDB configured by the gateway, as detailed below:
@@ -445,6 +445,7 @@ with sink (
'node-urls' = '10.53.53.53:9780', -- The URL of the data service port of the
DataNode node on the target IoTDB
```
**Notes: Currently supported gateway models**
+> For other models of network gateway devices, Please contact timechodb staff
to confirm compatibility.
| Gateway Type | Model
| Return Packet Limit | Send Limit |
| ---------------------- |
------------------------------------------------------------ |
------------------- | ---------------------- |
diff --git a/src/UserGuide/V1.3.x/User-Manual/Data-Sync-old_timecho.md
b/src/UserGuide/V1.3.x/User-Manual/Data-Sync-old_timecho.md
index 47671ea7..0fb36752 100644
--- a/src/UserGuide/V1.3.x/User-Manual/Data-Sync-old_timecho.md
+++ b/src/UserGuide/V1.3.x/User-Manual/Data-Sync-old_timecho.md
@@ -436,7 +436,7 @@ with sink (
This example is used to demonstrate the scenario where data from one IoTDB is
synchronized to another IoTDB through a unidirectional gateway, as shown in the
figure below:
-
+
In this example, the iotdb-air-gap-sink plugin in the sink task needs to be
used (currently supports some gateway models, for specific models, please
contact Timecho staff for confirmation). After configuring the gateway, execute
the following statement on A IoTDB. Fill in the node-urls with the URL of the
data service port of the DataNode node on the target IoTDB configured by the
gateway, as detailed below:
diff --git a/src/UserGuide/V1.3.x/User-Manual/Data-Sync_timecho.md
b/src/UserGuide/V1.3.x/User-Manual/Data-Sync_timecho.md
index 819ab8e5..b6132dba 100644
--- a/src/UserGuide/V1.3.x/User-Manual/Data-Sync_timecho.md
+++ b/src/UserGuide/V1.3.x/User-Manual/Data-Sync_timecho.md
@@ -433,7 +433,7 @@ with sink (
This example is used to demonstrate the scenario where data from one IoTDB is
synchronized to another IoTDB through a unidirectional gateway, as shown in the
figure below:
-
+
In this example, the iotdb-air-gap-sink plugin in the sink task needs to be
used . After configuring the gateway, execute the following statement on A
IoTDB. Fill in the node-urls with the URL of the data service port of the
DataNode node on the target IoTDB configured by the gateway, as detailed below:
@@ -445,6 +445,7 @@ with sink (
'node-urls' = '10.53.53.53:9780', -- The URL of the data service port of the
DataNode node on the target IoTDB
```
**Notes: Currently supported gateway models**
+> For other models of network gateway devices, Please contact timechodb staff
to confirm compatibility.
| Gateway Type | Model
| Return Packet Limit | Send Limit |
| ---------------------- |
------------------------------------------------------------ |
------------------- | ---------------------- |
diff --git a/src/UserGuide/dev-1.3/User-Manual/Data-Sync_timecho.md
b/src/UserGuide/dev-1.3/User-Manual/Data-Sync_timecho.md
index 819ab8e5..b6132dba 100644
--- a/src/UserGuide/dev-1.3/User-Manual/Data-Sync_timecho.md
+++ b/src/UserGuide/dev-1.3/User-Manual/Data-Sync_timecho.md
@@ -433,7 +433,7 @@ with sink (
This example is used to demonstrate the scenario where data from one IoTDB is
synchronized to another IoTDB through a unidirectional gateway, as shown in the
figure below:
-
+
In this example, the iotdb-air-gap-sink plugin in the sink task needs to be
used . After configuring the gateway, execute the following statement on A
IoTDB. Fill in the node-urls with the URL of the data service port of the
DataNode node on the target IoTDB configured by the gateway, as detailed below:
@@ -445,6 +445,7 @@ with sink (
'node-urls' = '10.53.53.53:9780', -- The URL of the data service port of the
DataNode node on the target IoTDB
```
**Notes: Currently supported gateway models**
+> For other models of network gateway devices, Please contact timechodb staff
to confirm compatibility.
| Gateway Type | Model
| Return Packet Limit | Send Limit |
| ---------------------- |
------------------------------------------------------------ |
------------------- | ---------------------- |
diff --git a/src/UserGuide/latest-Table/User-Manual/Data-Sync_timecho.md
b/src/UserGuide/latest-Table/User-Manual/Data-Sync_timecho.md
index cb83f253..21fe106c 100644
--- a/src/UserGuide/latest-Table/User-Manual/Data-Sync_timecho.md
+++ b/src/UserGuide/latest-Table/User-Manual/Data-Sync_timecho.md
@@ -421,7 +421,7 @@ WITH SINK (
This example demonstrates synchronizing data from one IoTDB to another through
a unidirectional air gap. The data pipeline is shown below:
-
+
In this example, the `iotdb-air-gap-sink` plugin is used (currently supports
specific air gap models; contact Timecho team for details). After configuring
the air gap, execute the following statement on IoTDB A, where `node-urls` is
the URL of the DataNode service port on the target IoTDB.
@@ -435,6 +435,20 @@ WITH SINK (
)
```
+**Notes: Currently supported gateway models**
+> For other models of network gateway devices, Please contact timechodb staff
to confirm compatibility.
+
+| Gateway Type | Model
| Return Packet Limit | Send Limit |
+| ---------------------- |
------------------------------------------------------------ |
------------------- | ---------------------- |
+| Forward Gate | NARI Syskeeper-2000 Forward Gate
| All 0 / All 1 bytes | No Limit |
+| Forward Gate | XJ Self-developed Diaphragm
| All 0 / All 1 bytes | No Limit |
+| Unknown | WISGAP | No Limit | No Limit |
+| Forward Gate | KEDONG StoneWall-2000 Network Security Isolation
Device | No Limit | No Limit |
+| Reverse Gate | NARI Syskeeper-2000 Reverse Direction
| All 0 / All 1 bytes | Meet E Language Format |
+| Unknown | DPtech ISG5000 | No Limit
| No Limit |
+| Unknown | GAP
+ XL—GAP | No Limit | No Limit |
+
### 3.7 Compressed Synchronization
IoTDB supports specifying data compression methods during synchronization. The
`compressor` parameter can be configured to enable real-time data compression
and transmission. Supported algorithms include `snappy`, `gzip`, `lz4`, `zstd`,
and `lzma2`. Multiple algorithms can be combined and applied in the configured
order. The `rate-limit-bytes-per-second` parameter (supported in V1.3.3 and
later) limits the maximum number of bytes transmitted per second (calculated
after compression). If [...]
diff --git a/src/UserGuide/latest/User-Manual/Data-Sync_timecho.md
b/src/UserGuide/latest/User-Manual/Data-Sync_timecho.md
index 4db26993..28098034 100644
--- a/src/UserGuide/latest/User-Manual/Data-Sync_timecho.md
+++ b/src/UserGuide/latest/User-Manual/Data-Sync_timecho.md
@@ -433,7 +433,7 @@ with sink (
This example is used to demonstrate the scenario where data from one IoTDB is
synchronized to another IoTDB through a unidirectional gateway, as shown in the
figure below:
-
+
In this example, the iotdb-air-gap-sink plugin in the sink task needs to be
used . After configuring the gateway, execute the following statement on A
IoTDB. Fill in the node-urls with the URL of the data service port of the
DataNode node on the target IoTDB configured by the gateway, as detailed below:
@@ -445,6 +445,7 @@ with sink (
'node-urls' = '10.53.53.53:9780', -- The URL of the data service port of the
DataNode node on the target IoTDB
```
**Notes: Currently supported gateway models**
+> For other models of network gateway devices, Please contact timechodb staff
to confirm compatibility.
| Gateway Type | Model
| Return Packet Limit | Send Limit |
| ---------------------- |
------------------------------------------------------------ |
------------------- | ---------------------- |
diff --git a/src/zh/UserGuide/Master/Table/User-Manual/Data-Sync_timecho.md
b/src/zh/UserGuide/Master/Table/User-Manual/Data-Sync_timecho.md
index 659aba8f..dde7a143 100644
--- a/src/zh/UserGuide/Master/Table/User-Manual/Data-Sync_timecho.md
+++ b/src/zh/UserGuide/Master/Table/User-Manual/Data-Sync_timecho.md
@@ -419,7 +419,7 @@ with sink (
本例子用来演示将一个 IoTDB 的数据，经过单向网闸，同步至另一个 IoTDB 的场景，数据链路如下图所示：
-
+
在这个例子中，需要使用 sink 任务中的 iotdb-air-gap-sink 插件，配置网闸后，在 A IoTDB 上执行下列语句，其中
node-urls 填写网闸配置的目标端 IoTDB 中 DataNode 节点的数据服务端口的 url，详细语句如下：
@@ -431,6 +431,7 @@ with sink (
)
```
**注意：目前支持的网闸型号**
+> 其他型号的网闸设备，请与天谋商务联系确认是否支持。
| 网闸类型 | 网闸型号 | 回包限制 | 发送限制
|
| ------------ | -------------------------------------------- |
----------------- | --------------- |
diff --git a/src/zh/UserGuide/Master/Tree/User-Manual/Data-Sync_timecho.md
b/src/zh/UserGuide/Master/Tree/User-Manual/Data-Sync_timecho.md
index c91ef222..66e4a73d 100644
--- a/src/zh/UserGuide/Master/Tree/User-Manual/Data-Sync_timecho.md
+++ b/src/zh/UserGuide/Master/Tree/User-Manual/Data-Sync_timecho.md
@@ -429,7 +429,7 @@ with sink (
本例子用来演示将一个 IoTDB 的数据，经过单向网闸，同步至另一个 IoTDB 的场景，数据链路如下图所示：
-
+
在这个例子中，需要使用 sink 任务中的 iotdb-air-gap-sink 插件，配置网闸后，在 A IoTDB 上执行下列语句，其中
node-urls 填写网闸配置的目标端 IoTDB 中 DataNode 节点的数据服务端口的 url，详细语句如下：
@@ -441,6 +441,7 @@ with sink (
)
```
**注意：目前支持的网闸型号**
+> 其他型号的网闸设备，请与天谋商务联系确认是否支持。
| 网闸类型 | 网闸型号 | 回包限制 | 发送限制
|
| ------------ | -------------------------------------------- |
----------------- | --------------- |
diff --git a/src/zh/UserGuide/V1.2.x/User-Manual/Data-Sync_timecho.md
b/src/zh/UserGuide/V1.2.x/User-Manual/Data-Sync_timecho.md
index 2a21afe7..ec8e0b7c 100644
--- a/src/zh/UserGuide/V1.2.x/User-Manual/Data-Sync_timecho.md
+++ b/src/zh/UserGuide/V1.2.x/User-Manual/Data-Sync_timecho.md
@@ -279,7 +279,7 @@ with connector (
本例子用来演示将一个 IoTDB 的数据，经过单向网闸，同步至另一个IoTDB的场景，数据链路如下图所示：
-
+
在这个例子中，需要使用 connector 任务中的iotdb-air-gap-connector
插件（目前支持部分型号网闸，具体型号请联系天谋科技工作人员确认），配置网闸后，在 A IoTDB 上执行下列语句，其中ip和port填写网闸信息，详细语句如下：
diff --git a/src/zh/UserGuide/V1.3.x/User-Manual/Data-Sync-old_timecho.md
b/src/zh/UserGuide/V1.3.x/User-Manual/Data-Sync-old_timecho.md
index cca2529e..e039fb2e 100644
--- a/src/zh/UserGuide/V1.3.x/User-Manual/Data-Sync-old_timecho.md
+++ b/src/zh/UserGuide/V1.3.x/User-Manual/Data-Sync-old_timecho.md
@@ -431,7 +431,7 @@ with sink (
本例子用来演示将一个 IoTDB 的数据，经过单向网闸，同步至另一个 IoTDB 的场景，数据链路如下图所示：
-
+
在这个例子中，需要使用 sink 任务中的 iotdb-air-gap-sink
插件（目前支持部分型号网闸，具体型号请联系天谋科技工作人员确认），配置网闸后，在 A IoTDB 上执行下列语句，其中 node-urls
填写网闸配置的目标端 IoTDB 中 DataNode 节点的数据服务端口的 url，详细语句如下：
diff --git a/src/zh/UserGuide/V1.3.x/User-Manual/Data-Sync_timecho.md
b/src/zh/UserGuide/V1.3.x/User-Manual/Data-Sync_timecho.md
index 7d9b059a..954e3d4b 100644
--- a/src/zh/UserGuide/V1.3.x/User-Manual/Data-Sync_timecho.md
+++ b/src/zh/UserGuide/V1.3.x/User-Manual/Data-Sync_timecho.md
@@ -429,7 +429,7 @@ with sink (
本例子用来演示将一个 IoTDB 的数据，经过单向网闸，同步至另一个 IoTDB 的场景，数据链路如下图所示：
-
+
在这个例子中，需要使用 sink 任务中的 iotdb-air-gap-sink 插件，配置网闸后，在 A IoTDB 上执行下列语句，其中
node-urls 填写网闸配置的目标端 IoTDB 中 DataNode 节点的数据服务端口的 url，详细语句如下：
@@ -441,6 +441,7 @@ with sink (
)
```
**注意：目前支持的网闸型号**
+> 其他型号的网闸设备，请与天谋商务联系确认是否支持。
| 网闸类型 | 网闸型号 | 回包限制 | 发送限制
|
| ------------ | -------------------------------------------- |
----------------- | --------------- |
diff --git a/src/zh/UserGuide/dev-1.3/User-Manual/Data-Sync_timecho.md
b/src/zh/UserGuide/dev-1.3/User-Manual/Data-Sync_timecho.md
index 7d9b059a..e9a71bfc 100644
--- a/src/zh/UserGuide/dev-1.3/User-Manual/Data-Sync_timecho.md
+++ b/src/zh/UserGuide/dev-1.3/User-Manual/Data-Sync_timecho.md
@@ -429,7 +429,7 @@ with sink (
本例子用来演示将一个 IoTDB 的数据，经过单向网闸，同步至另一个 IoTDB 的场景，数据链路如下图所示：
-
+
在这个例子中，需要使用 sink 任务中的 iotdb-air-gap-sink 插件，配置网闸后，在 A IoTDB 上执行下列语句，其中
node-urls 填写网闸配置的目标端 IoTDB 中 DataNode 节点的数据服务端口的 url，详细语句如下：
@@ -442,6 +442,8 @@ with sink (
```
**注意：目前支持的网闸型号**
+> 其他型号的网闸设备，请与天谋商务联系确认是否支持。
+
| 网闸类型 | 网闸型号 | 回包限制 | 发送限制
|
| ------------ | -------------------------------------------- |
----------------- | --------------- |
| 正向型 | 南瑞 Syskeeper-2000 正向型 | 全 0 / 全 1 bytes | 无限制
|
diff --git a/src/zh/UserGuide/latest-Table/User-Manual/Data-Sync_timecho.md
b/src/zh/UserGuide/latest-Table/User-Manual/Data-Sync_timecho.md
index 659aba8f..dde7a143 100644
--- a/src/zh/UserGuide/latest-Table/User-Manual/Data-Sync_timecho.md
+++ b/src/zh/UserGuide/latest-Table/User-Manual/Data-Sync_timecho.md
@@ -419,7 +419,7 @@ with sink (
本例子用来演示将一个 IoTDB 的数据，经过单向网闸，同步至另一个 IoTDB 的场景，数据链路如下图所示：
-
+
在这个例子中，需要使用 sink 任务中的 iotdb-air-gap-sink 插件，配置网闸后，在 A IoTDB 上执行下列语句，其中
node-urls 填写网闸配置的目标端 IoTDB 中 DataNode 节点的数据服务端口的 url，详细语句如下：
@@ -431,6 +431,7 @@ with sink (
)
```
**注意：目前支持的网闸型号**
+> 其他型号的网闸设备，请与天谋商务联系确认是否支持。
| 网闸类型 | 网闸型号 | 回包限制 | 发送限制
|
| ------------ | -------------------------------------------- |
----------------- | --------------- |
diff --git a/src/zh/UserGuide/latest/User-Manual/Data-Sync_timecho.md
b/src/zh/UserGuide/latest/User-Manual/Data-Sync_timecho.md
index c91ef222..66e4a73d 100644
--- a/src/zh/UserGuide/latest/User-Manual/Data-Sync_timecho.md
+++ b/src/zh/UserGuide/latest/User-Manual/Data-Sync_timecho.md
@@ -429,7 +429,7 @@ with sink (
本例子用来演示将一个 IoTDB 的数据，经过单向网闸，同步至另一个 IoTDB 的场景，数据链路如下图所示：
-
+
在这个例子中，需要使用 sink 任务中的 iotdb-air-gap-sink 插件，配置网闸后，在 A IoTDB 上执行下列语句，其中
node-urls 填写网闸配置的目标端 IoTDB 中 DataNode 节点的数据服务端口的 url，详细语句如下：
@@ -441,6 +441,7 @@ with sink (
)
```
**注意：目前支持的网闸型号**
+> 其他型号的网闸设备，请与天谋商务联系确认是否支持。
| 网闸类型 | 网闸型号 | 回包限制 | 发送限制
|
| ------------ | -------------------------------------------- |
----------------- | --------------- |
