This is an automated email from the ASF dual-hosted git repository. JackieTien97 pushed a commit to branch ty/pipe-edge in repository https://gitbox.apache.org/repos/asf/iotdb.git
commit 089f3ffff468a9faa87d2b349fed53fb4ef45682 Author: JackieTien97 <[email protected]> AuthorDate: Wed Sep 2 12:29:47 2026 +0800 Update pipe config for edge version --- .../assembly/resources/conf/edge/iotdb-system.properties | 14 ++++++++++++++ 1 file changed, 14 insertions(+) diff --git a/iotdb-core/node-commons/src/assembly/resources/conf/edge/iotdb-system.properties b/iotdb-core/node-commons/src/assembly/resources/conf/edge/iotdb-system.properties index 69902c87073..7ce4bc5922f 100644 --- a/iotdb-core/node-commons/src/assembly/resources/conf/edge/iotdb-system.properties +++ b/iotdb-core/node-commons/src/assembly/resources/conf/edge/iotdb-system.properties @@ -136,3 +136,17 @@ series_slot_num=1 # ---- metrics off (the internal MetricService is shared by both nodes) ---- cn_metric_level=OFF dn_metric_level=OFF + +# ---- realtime pipe sync out of the box ---- +# The pipe memory pool is 10% of the heap (~22MB at the default 224M budget), +# while the stock pipe memory estimates are sized for datacenter nodes: each +# pipe reserves a 15MB insert-node queue and estimates ~18MB more at task +# startup, so CREATE PIPE fails on an untuned edge node. Shrink the per-pipe +# queue budget and skip the startup estimation; actual allocations stay +# elastic within the pool, degrading to batched TsFile transfer on pressure. +# Validated on Raspberry Pi 4B: one realtime pipe ('history.enable'='false') +# forwarding a 100-points/s load adds ~20MB RSS and syncs with sub-second +# latency (single-record p99 < 500ms). +pipe_insert_node_queue_memory=2097152 +pipe_enable_memory_checked=false +pipe_logger_cache_max_size_in_bytes=1048576 \ No newline at end of file
