StefanieZhao7 commented on code in PR #436:
URL: https://github.com/apache/iotdb-docs/pull/436#discussion_r1857566105


##########
src/zh/UserGuide/latest/Preparatory-knowledge/Cluster-Concept.md:
##########
@@ -0,0 +1,55 @@
+<!--
+
+    Licensed to the Apache Software Foundation (ASF) under one
+    or more contributor license agreements.  See the NOTICE file
+    distributed with this work for additional information
+    regarding copyright ownership.  The ASF licenses this file
+    to you under the Apache License, Version 2.0 (the
+    "License"); you may not use this file except in compliance
+    with the License.  You may obtain a copy of the License at
+    
+        http://www.apache.org/licenses/LICENSE-2.0
+    
+    Unless required by applicable law or agreed to in writing,
+    software distributed under the License is distributed on an
+    "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+    KIND, either express or implied.  See the License for the
+    specific language governing permissions and limitations
+    under the License.
+
+-->
+
+# 集群相关概念
+下图展示了一个常见的 IoTDB 3C3D1A(3 个 ConfigNode、3 个 DataNode 和 1 个 AINode)的集群部署模式:
+<img style="width:100%; max-width:800px; max-height:600px; margin-left:auto; 
margin-right:auto; display:block;" 
src="https://alioss.timecho.com/docs/img/Common-Concepts_01.png";>
+
+其中包括了 IoTDB 集群使用中用户常接触到的几个概念,包括:
+- **节点**(ConfigNode、DataNode、AINode);
+- **槽**(SchemaSlot、DataSlot);
+- **Region**(SchemaRegion、DataRegion);
+- ***副本组***。
+
+下文将重点对以上概念进行介绍。
+
+## 节点
+IoTDB 集群包括三种节点(进程),**ConfigNode**(管理节点),**DataNode**(数据节点)和 
**AINode**(分析节点),如下所示:
+- **ConfigNode**:存储集群的配置信息、数据库的元数据、时间序列元数据和数据的路由信息,监控集群节点并实施负载均衡,所有 ConfigNode 
之间互为全量备份,如上图中的 ConfigNode-1,ConfigNode-2 和 ConfigNode-3 所示。ConfigNode 
不直接接收客户端读写请求,它会通过一系列[负载均衡算法](https://iotdb.apache.org/zh/UserGuide/latest/Technical-Insider/Cluster-data-partitioning.html)对集群中元数据和数据的分布提供指导。
+- **DataNode**:负责时间序列元数据和数据的读写,每个 DataNode 都能接收客户端读写请求并提供相应服务,如上图中的 
DataNode-1,DataNode-2 和 DataNode-3 所示。接收客户端读写请求时,若 DataNode 
缓存有对应的路由信息,它能直接在本地执行或是转发这些请求;否则它会向 ConfigNode 询问并缓存路由信息,以加速后续请求的服务效率。
+- **AINode**:负责与 ConfigNode 和 DataNode 交互来扩展 IoTDB 
集群对时间序列进行机器学习分析的能力,支持从外部引入已有机器学习模型进行注册,并使用注册的模型在指定时序数据上通过简单 SQL 
语句完成时序分析任务的过程,将模型的创建、管理及推理融合在数据库引擎中。目前已提供常见时序分析场景(例如预测与异常检测)的机器学习算法或自研模型。

Review Comment:
   机器学习分析->智能分析



##########
src/UserGuide/latest/Preparatory-knowledge/Cluster-Concept.md:
##########
@@ -0,0 +1,59 @@
+<!--
+
+    Licensed to the Apache Software Foundation (ASF) under one
+    or more contributor license agreements.  See the NOTICE file
+    distributed with this work for additional information
+    regarding copyright ownership.  The ASF licenses this file
+    to you under the Apache License, Version 2.0 (the
+    "License"); you may not use this file except in compliance
+    with the License.  You may obtain a copy of the License at
+    
+        http://www.apache.org/licenses/LICENSE-2.0
+    
+    Unless required by applicable law or agreed to in writing,
+    software distributed under the License is distributed on an
+    "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+    KIND, either express or implied.  See the License for the
+    specific language governing permissions and limitations
+    under the License.
+
+-->
+
+# Cluster-related Concepts
+The figure below illustrates a typical IoTDB 3C3D1A cluster deployment mode, 
comprising 3 ConfigNodes, 3 DataNodes, and 1 AINode:  
+<img style="width:100%; max-width:800px; max-height:600px; margin-left:auto; 
margin-right:auto; display:block;" 
src="https://alioss.timecho.com/docs/img/Common-Concepts_02.png";>
+
+This deployment involves several key concepts that users commonly encounter 
when working with IoTDB clusters, including:  
+- **Nodes** (ConfigNode, DataNode, AINode);  
+- **Slots** (SchemaSlot, DataSlot);  
+- **Regions** (SchemaRegion, DataRegion);  
+- **Replica Groups**.
+
+The following sections will provide a detailed introduction to these concepts.
+
+## Nodes
+
+An IoTDB cluster consists of three types of nodes (processes): **ConfigNode** 
(the main node), **DataNode**, and **AINode**, as detailed below:
+- **ConfigNode:** ConfigNodes store cluster configurations, database metadata, 
the routing information of time series' schema and data. They also monitor 
cluster nodes and conduct load balancing. All ConfigNodes maintain full mutual 
backups, as shown in the figure with ConfigNode-1, ConfigNode-2, and 
ConfigNode-3. ConfigNodes do not directly handle client read or write requests. 
Instead, they guide the distribution of time series' schema and data within the 
cluster using a series of [load balancing 
algorithms](https://iotdb.apache.org/UserGuide/latest/Technical-Insider/Cluster-data-partitioning.html).
+- **DataNode:** DataNodes are responsible for reading and writing time series' 
schema and data. Each DataNode can accept client read and write requests and 
provide corresponding services, as illustrated with DataNode-1, DataNode-2, and 
DataNode-3 in the above figure. When a DataNode receives client requests, it 
can process them directly or forward them if it has the relevant routing 
information cached locally. Otherwise, it queries the ConfigNode for routing 
details and caches the information to improve the efficiency of subsequent 
requests.
+- **AINode:** AINodes interact with ConfigNodes and DataNodes to extend 
IoTDB's capabilities for machine learning analysis on time series data. They 
support registering pre-trained machine learning models from external sources 
and performing time series analysis tasks using simple SQL statements on 
specified data. This process integrates model creation, management, and 
inference within the database engine. Currently, the system provides built-in 
algorithms or custom models for common time series analysis scenarios, such as 
forecasting and anomaly detection.

Review Comment:
   machine learning analysis-> data intelligence analysis
   custom models -> self-training models



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to