Merge pull request #12490 from taosdata/docs/TD-15576

docs: English version of Administration chapter

docs-en/13-operation/01-pkg-install.md

 ---
-title: 安装和卸载
-description: 安装、卸载、启动、停止和升级
+title: Install & Uninstall
+description: Install, Uninstall, Start, Stop and Upgrade
 ---
 
 import Tabs from "@theme/Tabs";
 import TabItem from "@theme/TabItem";
 
-TDengine 开源版本提供 deb 和 rpm 格式安装包，用户可以根据自己的运行环境选择合适的安装包。其中 deb 支持 Debian/Ubuntu 及衍生系统，rpm 支持 CentOS/RHEL/SUSE 及衍生系统。同时我们也为企业用户提供 tar.gz 格式安装包。
+TDengine community version provides dev and rpm package for users to choose based on the system environment. deb supports Debian, Ubuntu and systems derived from them. rpm supports CentOS, RHEL, SUSE and systems derived from them. Furthermore, tar.gz package is provided for enterprise customers.
 
-## 安装
+## Install
 
 <Tabs>
-<TabItem label="Deb 安装" value="debinst">
+<TabItem label="Install Deb" value="debinst">
 
-1、从官网下载获得 deb 安装包，例如 TDengine-server-2.4.0.7-Linux-x64.deb；
-2、进入到 TDengine-server-2.4.0.7-Linux-x64.deb 安装包所在目录，执行如下的安装命令：
+1. Download deb package from official website, for example TDengine-server-2.4.0.7-Linux-x64.deb
+2. In the directory where the package is located, execute below command
 
-```
+```bash
 $ sudo dpkg -i TDengine-server-2.4.0.7-Linux-x64.deb
 (Reading database ... 137504 files and directories currently installed.)
 Preparing to unpack TDengine-server-2.4.0.7-Linux-x64.deb ...
@@ -43,10 +43,10 @@ TDengine is installed successfully!
 
 </TabItem>
 
-<TabItem label="RPM 安装" value="rpminst">
+<TabItem label="Install RPM" value="rpminst">
 
-1、从官网下载获得 rpm 安装包，例如 TDengine-server-2.4.0.7-Linux-x64.rpm；
-2、进入到 TDengine-server-2.4.0.7-Linux-x64.rpm 安装包所在目录，执行如下的安装命令：
+1. Download rpm package from official website, for example TDengine-server-2.4.0.7-Linux-x64.rpm；
+2. In the directory where the package is located, execute below command
 
 ```
 $ sudo rpm -ivh TDengine-server-2.4.0.7-Linux-x64.rpm
@@ -74,12 +74,12 @@ TDengine is installed successfully!
 
 </TabItem>
 
-<TabItem label="tar.gz 安装" value="tarinst">
+<TabItem label="Install tar.gz" value="tarinst">
 
-1、从官网下载获得 tar.gz 安装包，例如 TDengine-server-2.4.0.7-Linux-x64.tar.gz；
-2、进入到 TDengine-server-2.4.0.7-Linux-x64.tar.gz 安装包所在目录，先解压文件后，进入子目录，执行其中的 install.sh 安装脚本：
+1. Download the tar.gz package, for example TDengine-server-2.4.0.7-Linux-x64.tar.gz；
+   2、In the directory where the package is located, firstly decompress the file, then switch to the sub-directory generated in decompressing, i.e. "TDengine-enterprise-server-2.4.0.7/" in this example, and execute the `install.sh` script.
 
-```
+```bash
 $ tar xvzf TDengine-enterprise-server-2.4.0.7-Linux-x64.tar.gz
 TDengine-enterprise-server-2.4.0.7/
 TDengine-enterprise-server-2.4.0.7/driver/
@@ -124,7 +124,7 @@ taoskeeper is installed, enable it by `systemctl enable taoskeeper`
 ```
 
 :::info
-install.sh 安装脚本在执行过程中，会通过命令行交互界面询问一些配置信息。如果希望采取无交互安装方式，那么可以用 -e no 参数来执行 install.sh 脚本。运行 `./install.sh -h` 指令可以查看所有参数的详细说明信息。
+Some configuration will be prompted for users to provide when install.sh is executing, the interactive mode can be disabled by executing `./install.sh -e no`. `./install -h` can show all parameters and detailed explanation.
 
 :::
 
@@ -132,18 +132,18 @@ install.sh 安装脚本在执行过程中，会通过命令行交互界面询问
 </Tabs>
 
 :::note
-当安装第一个节点时，出现 Enter FQDN：提示的时候，不需要输入任何内容。只有当安装第二个或以后更多的节点时，才需要输入已有集群中任何一个可用节点的 FQDN，支持该新节点加入集群。当然也可以不输入，而是在新节点启动前，配置到新节点的配置文件中。
+When installing on the first node in the cluster, when "Enter FQDN:" is prompted, nothing needs to be provided. When installing on following nodes, when "Enter FQDN:" is prompted, the end point of the first dnode in the cluster can be input if it has been already up; or just ignore it and configure later after installation is done.
 
 :::
 
-## 卸载
+## Uninstall
 
 <Tabs>
-<TabItem label="Deb 卸载" value="debuninst">
+<TabItem label="Uninstall Deb" value="debuninst">
 
-卸载命令如下:
+Deb package of TDengine can be uninstalled as below:
 
-```
+```bash
 $ sudo dpkg -r tdengine
 (Reading database ... 137504 files and directories currently installed.)
 Removing tdengine (2.4.0.7) ...
@@ -153,9 +153,9 @@ TDengine is removed successfully!
 
 </TabItem>
 
-<TabItem label="RPM 卸载" value="rpmuninst">
+<TabItem label="Uninstall RPM" value="rpmuninst">
 
-卸载命令如下:
+RPM package of TDengine can be uninstalled as below:
 
 ```
 $ sudo rpm -e tdengine
@@ -164,9 +164,9 @@ TDengine is removed successfully!
 
 </TabItem>
 
-<TabItem label="tar.gz 卸载" value="taruninst">
+<TabItem label="Uninstall tar.gz" value="taruninst">
 
-卸载命令如下:
+tar.gz package of TDengine can be uninstalled as below:
 
 ```
 $ rmtaos
@@ -179,32 +179,28 @@ taosKeeper is removed successfully!
 </TabItem>
 </Tabs>
 
-:::info
-- TDengine 提供了多种安装包，但最好不要在一个系统上同时使用 tar.gz 安装包和 deb 或 rpm 安装包。否则会相互影响，导致在使用时出现问题。
+:::note
 
-- 对于 deb 包安装后，如果安装目录被手工误删了部分，出现卸载、或重新安装不能成功。此时，需要清除 TDengine 包的安装信息，执行如下命令：
+- It's strongly suggested not to use multiple kinds of installation packages on single host TDengine
+- After deb package is installed, if the installation directory is removed manually so that uninstall or reinstall can't succeed, it can be resolved by cleaning up TDengine package information as below command and then reinstalling.
 
-   ```
+```bash
    $ sudo rm -f /var/lib/dpkg/info/tdengine*
-   ```
-
-然后再重新进行安装就可以了。
+```
 
-- 对于 rpm 包安装后，如果安装目录被手工误删了部分，出现卸载、或重新安装不能成功。此时，需要清除 TDengine 包的安装信息，执行如下命令：
+- After rpm package is installed, if the installation directory is removed manually so that uninstall or reinstall can't succeed, it can be resolved by cleaning up TDengine package information as below command and then reinstalling.
 
-   ```
+```bash
    $ sudo rpm -e --noscripts tdengine
-   ```
-
-然后再重新进行安装就可以了。
+```
 
 :::
 
-## 安装目录说明
+## Installation Directory
 
-TDengine 成功安装后，主安装目录是 /usr/local/taos，目录内容如下：
+TDengine is installed at /usr/local/taos if successful.
 
-```
+```bash
 $ cd /usr/local/taos
 $ ll
 $ ll
@@ -220,64 +216,67 @@ drwxr-xr-x  2 root root 4096 Feb 22 09:34 include/
 lrwxrwxrwx  1 root root   13 Feb 22 09:34 log -> /var/log/taos/
 ```
 
-- 自动生成配置文件目录、数据库目录、日志目录。
-- 配置文件缺省目录：/etc/taos/taos.cfg， 软链接到 /usr/local/taos/cfg/taos.cfg；
-- 数据库缺省目录：/var/lib/taos， 软链接到 /usr/local/taos/data；
-- 日志缺省目录：/var/log/taos， 软链接到 /usr/local/taos/log；
-- /usr/local/taos/bin 目录下的可执行文件，会软链接到 /usr/bin 目录下；
-- /usr/local/taos/driver 目录下的动态库文件，会软链接到 /usr/lib 目录下；
-- /usr/local/taos/include 目录下的头文件，会软链接到到 /usr/include 目录下；
+During the installation process:
+
+- Configuration directory, data directory, and log directory are created automatically if they don't exist
+- The default configuration file is located at /etc/taos/taos.cfg, which is a copy of /usr/local/taos/cfg/taos.cfg if not existing
+- The default data directory is /var/lib/taos, which is a soft link to /usr/local/taos/data
+- The default log directory is /var/log/taos, which is a soft link to /usr/local/taos/log
+- The executables at /usr/local/taos/bin are linked to /usr/bin
+- The DLL files at /usr/local/taos/driver are linked to /usr/lib
+- The header files at /usr/local/taos/include are linked to /usr/include
+
+:::note
 
-## 卸载和更新文件说明
+- When TDengine is uninstalled, the configuration /etc/taos/taos.cfg, data directory /var/lib/taos, log directory /var/log/taos are kept. They can be deleted manually with caution because data can't be recovered once
+- When reinstalling TDengine, if the default configuration file /etc/taos/taos.cfg exists, it will be kept and the configuration file in the installation package will be renamed to taos.cfg.orig and stored at /usr/loca/taos/cfg to be used as configuration sample. Otherwise the configuration file in the installation package will be installed to /etc/taos/taos.cfg and used.
 
-卸载安装包的时候，将保留配置文件、数据库文件和日志文件，即 /etc/taos/taos.cfg 、 /var/lib/taos 、 /var/log/taos 。如果用户确认后不需保留，可以手工删除，但一定要慎重，因为删除后，数据将永久丢失，不可以恢复！
+## Start and Stop
 
-如果是更新安装，当缺省配置文件（ /etc/taos/taos.cfg ）存在时，仍然使用已有的配置文件，安装包中携带的配置文件修改为 taos.cfg.orig 保存在 /usr/local/taos/cfg/ 目录，可以作为设置配置参数的参考样例；如果不存在配置文件，就使用安装包中自带的配置文件。
+Linux system services `systemd`, `systemctl` or `service` is used to start, stop and restart TDengine. The server process of TDengine is `taosd`, which is started automatically after the Linux system is started. System operator can use `systemd`, `systemctl` or `service` to start, stop or restart TDengine server.
 
-## 启动和停止
+For example, if using `systemctl` , the commands to start, stop, restart and check TDengine server are as below:
 
-TDengine 使用 Linux 系统的 systemd/systemctl/service 来管理系统的启动和、停止、重启操作。TDengine 的服务进程是 taosd，默认情况下 TDengine 在系统启动后将自动启动。DBA 可以通过 systemd/systemctl/service 手动操作停止、启动、重新启动服务。
+- Start server：`systemctl start taosd`
 
-以 systemctl 为例，命令如下：
+- Stop server：`systemctl stop taosd`
 
-- 启动服务进程：`systemctl start taosd`
+- Restart server：`systemctl restart taosd`
 
-- 停止服务进程：`systemctl stop taosd`
+- Check server status：`systemctl status taosd`
 
-- 重启服务进程：`systemctl restart taosd`
+From version 2.4.0.0, a new independent component named as `taosAdapter` has been included in TDengine. `taosAdapter` should be started and stopped using `systemctl`.
 
-- 查看服务状态：`systemctl status taosd`
+If the server process is OK, the output of `systemctl status` is like below:
 
-注意：TDengine 在 2.4 版本之后包含一个独立组件 taosAdapter 需要使用 systemctl 命令管理 taosAdapter 服务的启动和停止。
+```
+Active: active (running)
+```
 
-如果服务进程处于活动状态，则 status 指令会显示如下的相关信息：
+Otherwise, the output is as below:
 
-   ```
-   Active: active (running)
-   ```
+```
+Active: inactive (dead)
+```
 
-如果后台服务进程处于停止状态，则 status 指令会显示如下的相关信息：
+## Upgrade
 
-   ```
-   Active: inactive (dead)
-   ```
+There are two aspects in upgrade operation: upgrade installation package and upgrade a running server.
 
-## 升级
-升级分为两个层面：升级安装包 和 升级运行中的实例。
+Upgrading package should follow the steps mentioned previously to firstly uninstall old version then install new version.
 
-升级安装包请遵循前述安装和卸载的步骤先卸载旧版本再安装新版本。
+Upgrading a running server is much more complex. Firstly please check the version number of old version and new version. The version number of TDengine consists of 4 sections, only the first 3 section match can the old version be upgraded to the new version. The steps of upgrading a running server are as below:
 
-升级运行中的实例则要复杂得多，首先请注意版本号，TDengine 的版本号目前分为四段，如 2.4.0.14 和 2.4.0.16，只有前三段版本号一致（即只有第四段版本号不同）才能把一个运行中的实例进行升级。升级步骤如下：
-- 停止数据写入
-- 确保所有数据落盘，即写入时序数据库
-- 停止 TDengine 集群
-- 卸载旧版本并安装新版本
-- 重新启动 TDengine 集群
-- 进行简单的查询操作确认旧数据没有丢失 
-- 进行简单的写入操作确认 TDengine 集群可用
-- 重新恢复业务数据的写入
+- Stop inserting data
+- Make sure all data persisted into disk
+- Stop the cluster of TDengine
+- Uninstall old version and install new version
+- Start the cluster of TDengine
+- Make some simple queries to make sure no data loss
+- Make some simple data insertion to make sure the cluster works well
+- Restore business data
 
 :::warning
-TDengine 不保证低版本能够兼容高版本的数据，所以任何时候都不推荐降级
+TDengine doesn't guarantee any lower version is compatible with the data generated by a higher version, so it's never recommended to downgrade the version.
 
 :::

docs-en/13-operation/02-planning.mdx

 ---
-sidebar_label: 容量规划
-title: 容量规划
+sidebar_label: Planning
+title: Capacity Planning
 ---
 
-使用 TDengine 来搭建一个物联网大数据平台，计算资源、存储资源需要根据业务场景进行规划。下面分别讨论系统运行所需要的内存、CPU 以及硬盘空间。
+The computing and storage resources need to be planned if using TDengine to build an IoT platform. How to plan the CPU, memory and disk required will be described in this chapter.
 
-## 内存需求
+## Memory Requirement of Server Side
 
-每个 Database 可以创建固定数目的 vgroup，默认与 CPU 核数相同，可通过 maxVgroupsPerDb 配置；vgroup 中的每个副本会是一个 vnode；每个 vnode 会占用固定大小的内存（大小与数据库的配置参数 blocks 和 cache 有关)；每个 Table 会占用与标签总长度有关的内存；此外，系统会有一些固定的内存开销。因此，每个 DB 需要的系统内存可通过如下公式计算：
+The number of vgroups created for each database is same as the number of CPU cores by default and can be configured by parameter `maxVgroupsPerDb`, each vnode in a vgroup stores one replica. Each vnode consumes fixed size of memory, i.e. `blocks` \* `cache`. Besides, some memory is required for tag values associated with each table. A fixed amount of memory is required for each cluster. So, the memory required for each DB can be calculated using below formula:
 
 ```
 Database Memory Size = maxVgroupsPerDb * replica * (blocks * cache + 10MB) + numOfTables * (tagSizePerTable + 0.5KB)
 ```
 
-示例：假设 maxVgroupPerDB 是缺省值 64，cache 是缺省大小 16M, blocks 是缺省值 6，并且一个 DB 中有 10 万张表，单副本，标签总长度是 256 字节，则这个 DB 总的内存需求为：64 \* 1 \* (16 \* 6 + 10) + 100000 \* (0.25 + 0.5) / 1000 = 6792M。
+For example, assuming the default value of `maxVgroupPerDB` is 64, the default value of `cache` 16M, the default value of `blocks` is 6, there are 100,000 tables in a DB, the replica number is 1, total length of tag values is 256 bytes, the total memory required for this DB is: 并且一个 DB 中有 10 万张表，单副本，标签总长度是 256 字节，则这个 DB 总的内存需求为：64 \* 1 \* (16 \* 6 + 10) + 100000 \* (0.25 + 0.5) / 1000 = 6792M.
 
-在实际的系统运维中，我们通常会更关心 TDengine 服务进程（taosd）会占用的内存量。
+In real operation of TDengine, we are more concerned about the memory used by each TDengine server process `taosd`.在
 
 ```
-taosd 内存总量 = vnode 内存 + mnode 内存 + 查询内存
+    taosd_memory = vnode_memory + mnode_memory + query_memory
 ```
 
-其中：
+In the above formula:
 
-1. “vnode 内存”指的是集群中所有的 Database 存储分摊到当前 taosd 节点上所占用的内存资源。可以按上文“Database Memory Size”计算公式估算每个 DB 的内存占用量进行加总，再按集群中总共的 TDengine 节点数做平均（如果设置为多副本，则还需要乘以对应的副本倍数）。
-2. “mnode 内存”指的是集群中管理节点所占用的资源。如果一个 taosd 节点上分布有 mnode 管理节点，则内存消耗还需要增加“0.2KB \* 集群中数据表总数”。
-3. “查询内存”指的是服务端处理查询请求时所需要占用的内存。单条查询语句至少会占用“0.2KB \* 查询涉及的数据表总数”的内存量。
+1. "vnode_memory" of a `taosd` process is the memory used by all vnodes hosted by this `taosd` process. It can be roughly calculated by firstly adding up the total memory of all DBs whose memory usage can be derived according to the formula mentioned previously then dividing by number of dnodes and multiplying the number of replicas.
 
-注意：以上内存估算方法，主要讲解了系统的“必须内存需求”，而不是“内存总数上限”。在实际运行的生产环境中，由于操作系统缓存、资源管理调度等方面的原因，内存规划应当在估算结果的基础上保留一定冗余，以维持系统状态和系统性能的稳定性。并且，生产环境通常会配置系统资源的监控工具，以便及时发现硬件资源的紧缺情况。
+```
+    vnode_memory = sum(Database memory) / number_of_dnodes \* replica
+```
+
+2. "mnode_memory" of a `taosd` process is the memory consumed by a mnode. If there is one (and only one) mnode hosted in a `taosd` process, the memory consumed by "mnode" is "0.2KB \* the total number of tables in the cluster".
 
-最后，如果内存充裕，可以考虑加大 Blocks 的配置，这样更多数据将保存在内存里，提高写入和查询速度。
+3. "query_memory" is the memory used when processing query requests. Each ongoing query consumes at least "0.2 KB \* total number of involved tables".
 
-### 客户端内存需求
+Please be noted that the above formulas can only be used to estimate the minimum memory requirement, instead of maximum memory usage. In a real production environment, it's better to preserve some redundance beyond the estimated minimum memory requirement. If memory is abundant, it's suggested to increase the value of parameter `blocks` to speed up data insertion and data query.
 
-客户端应用采用 taosc 客户端驱动连接服务端，会有内存需求的开销。
+## Memory Requirement of Client Side
 
-客户端的内存开销主要由写入过程中的 SQL 语句、表的元数据信息缓存、以及结构性开销构成。系统最大容纳的表数量为 N（每个通过超级表创建的表的 meta data 开销约 256 字节），最大并行写入线程数量 T，最大 SQL 语句长度 S（通常是 1 Mbytes）。由此可以进行客户端内存开销的估算（单位 MBytes）：
+The client programs use TDengine client driver `taosc` to connect to the server side, there is also memory requirement for a client program.
+
+The memory consumed by a client program is mainly about the SQL statements for data insertion, caching of table metadata, and some internal use. Assuming maximum number of tables is N (the memory consumed by the metadata of each table is 256 bytes), maximum number of threads for parallel insertion is T, maximum length of a SQL statement is S (normally 1 MB), the memory required by a client program can be estimated using below formula:
 
 ```
 M = (T * S * 3 + (N / 4096) + 100)
 ```
 
-举例如下：用户最大并发写入线程数 100，子表数总数 10,000,000，那么客户端的内存最低要求是：
+For example, if the number of parallel data insertion threads is 100, total number of tables is 10,000,000, then minimum memory requirement of a client program is:
 
 ```
 100 * 3 + (10000000 / 4096) + 100 = 2741 (MBytes)
 ```
 
-即配置 3 GBytes 内存是最低要求。
+So, at least 3GB needs to be reserved for such a client.
 
-## CPU 需求
+## CPU Requirement
 
-CPU 的需求取决于如下两方面：
+The CPU resources required depend on two aspects:
 
-- **数据插入** TDengine 单核每秒能至少处理一万个插入请求。每个插入请求可以带多条记录，一次插入一条记录与插入 10 条记录，消耗的计算资源差别很小。因此每次插入，条数越大，插入效率越高。如果一个插入请求带 200 条以上记录，单核就能达到每秒插入 100 万条记录的速度。但对前端数据采集的要求越高，因为需要缓存记录，然后一批插入。
-- **查询需求** TDengine 提供高效的查询，但是每个场景的查询差异很大，查询频次变化也很大，难以给出客观数字。需要用户针对自己的场景，写一些查询语句，才能确定。
+- **Data Insertion** Each dnode of TDengine can process at least 10,000 insertion requests in one second, while each insertion request can have multiple rows. The computing resource consumed between inserting 1 row one time and inserting 10 rows one time is very small. So, the more the rows to insert one time, the higher the efficiency. Inserting in bach also exposes requirement for the client side which needs to cache rows and insert in batch once the cached rows reaches a threshold.
+- **Data Query** High efficiency query is provided in TDengine, but it's hard to estimate the CPU resource required because the queries used in different use cases and the frequency of queries vary significantly. It can only be verified with the query statements, query frequency, data size to be queried, etc provided by user.
 
-因此仅对数据插入而言，CPU 是可以估算出来的，但查询所耗的计算资源无法估算。在实际运营过程中，不建议 CPU 使用率超过 50%，超过后，需要增加新的节点，以获得更多计算资源。
+In short words, the CPU resource required for data insertion can be estimated but it's hard to do so for query use cases. In real operation, it's suggested to control CPU usage below 50%. If this threshold is exceeded, it's a reminder for system operator to add more nodes in the cluster to expand resources.
 
-## 存储需求
+## Disk Requirement
 
-TDengine 相对于通用数据库，有超高的压缩比，在绝大多数场景下，TDengine 的压缩比不会低于 5 倍，有的场合，压缩比可达到 10 倍以上，取决于实际场景的数据特征。压缩前的原始数据大小可通过如下方式计算：
+The compression ratio in TDengine is much higher than that in RDBMS. In most cases, the compression ratio in TDengine is bigger than 5, or even 10 in some cases, depending on the characteristics of the original data. The data size before compression can be calculated based on below formula:
 
 ```
 Raw DataSize = numOfTables * rowSizePerTable * rowsPerTable
 ```
 
-示例：1000 万台智能电表，每台电表每 15 分钟采集一次数据，每次采集的数据 128 字节，那么一年的原始数据量是：10000000 \* 128 \* 24 \* 60 / 15 \* 365 = 44.8512T。TDengine 大概需要消耗 44.851 / 5 = 8.97024T 空间。
-
-用户可以通过参数 keep，设置数据在磁盘中的最大保存时长。为进一步减少存储成本，TDengine 还提供多级存储，最冷的数据可以存放在最廉价的存储介质上，应用的访问不用做任何调整，只是读取速度降低了。
+For example, there are 10,000,000 meters, while each meter collects data every 15 minutes and the data size of each collection si 128 bytes, so the raw data size of one year is: 10000000 \* 128 \* 24 \* 60 / 15 \* 365 = 44.8512(TB). Assuming compression ratio is 5, the actual disk size is: 44.851 / 5 = 8.97024(TB).
 
-为提高速度，可以配置多块硬盘，这样可以并发写入或读取数据。需要提醒的是，TDengine 采取多副本的方式提供数据的高可靠，因此不再需要采用昂贵的磁盘阵列。
+Parameter `keep` can be used to set how long the data will be kept on disk. To further reduce storage cost, multiple storage levels can be enabled in TDengine, with the coldest data stored on the cheapest storage device, and this is transparent to application programs.
 
-## 物理机或虚拟机台数
+To increase the performance, multiple disks can be setup for parallel data reading or data inserting. Please be noted that expensive disk array is not necessary because replications are used in TDengine to provide high availability.
 
-根据上面的内存、CPU、存储的预估，就可以知道整个系统需要多少核、多少内存、多少存储空间。如果数据副本数不为 1，总需求量需要再乘以副本数。
+## Number of Hosts
 
-因为 TDengine 具有很好的水平扩展能力，根据总量，再根据单个物理机或虚拟机的资源，就可以轻松决定需要购置多少台物理机或虚拟机了。
+A host can be either physical or virtual. The total memory, total CPU, total disk required can be estimated according to the formulas mentioned previously. Then, according to the system resources that a single host can provide, assuming all hosts are same in resources, the number of hosts can be derived easily.
 
-**立即计算 CPU、内存、存储，请参见：[资源估算方法](https://www.taosdata.com/config/config.html)。**
+**Quick Estimation for CPU, Memory and Disk** Please refer to [Resource Estimate](https://www.taosdata.com/config/config.html).

docs-en/13-operation/03-tolerance.md

 ---
-title: 容错和灾备
+sidebar_label: Tolerance
+title: Tolerance and Disaster Recovery
 ---
 
-## 容错
+## Tolerance
 
-TDengine 支持**WAL**（Write Ahead Log）机制，实现数据的容错能力，保证数据的高可用。
+TDengine uses **WAL**, i.e. Write Ahead Log, to achieve fault tolerance and make sure high availability.
 
-TDengine 接收到应用的请求数据包时，先将请求的原始数据包写入数据库日志文件，等数据成功写入数据库数据文件后，再删除相应的 WAL。这样保证了 TDengine 能够在断电等因素导致的服务重启时从数据库日志文件中恢复数据，避免数据的丢失。
+When a data block is received by TDengine, the original data block is firstly written into WAL. The log in WAL will be deleted only after the data has been written into data files in the database. Data can be recovered from WAL in case the server is stopped abnormally due to any reason and then restarted.
 
-涉及的系统配置参数有两个：
+There are 2 configuration parameters related to WAL:
 
-- walLevel：WAL 级别，0：不写 wal; 1：写 wal, 但不执行 fsync; 2：写 wal, 而且执行 fsync。
-- fsync：当 walLevel 设置为 2 时，执行 fsync 的周期。设置为 0，表示每次写入，立即执行 fsync。
+- walLevel：0：wal is disabled; 1：wal is enabled without fsync; 2：wal is enabled with fsync.
+- fsync：only valid when walLevel is set to 2, it specified the interval of invoking fsync. If set to 0, it means fsync is invoked immediately once WAL is written.
 
-如果要 100%的保证数据不丢失，需要将 walLevel 设置为 2，fsync 设置为 0。这时写入速度将会下降。但如果应用侧启动的写数据的线程数达到一定的数量(超过 50)，那么写入数据的性能也会很不错，只会比 fsync 设置为 3000 毫秒下降 30%左右。
+To achieve absolutely no data loss, walLevel needs to be set to 2 and fsync needs to be set to 1. The penalty is the speed of data insertion downgrades. However, if the concurrent threads of data insertion on the client side can reach a big enough number, for example 50, the data insertion performance would be still good enough, our verification shows that the drop is only 30% compared to fsync is set to 3,000 milliseconds.
 
-## 灾备
+## Disaster Recovery
 
-TDengine 的集群通过多个副本的机制，来提供系统的高可用性，实现灾备能力。
+TDengine uses replications to provide high availability and disaster recovery capability.
 
-TDengine 集群是由 mnode 负责管理的，为保证 mnode 的高可靠，可以配置多个 mnode 副本，副本数由系统配置参数 numOfMnodes 决定，为了支持高可靠，需要设置大于 1。为保证元数据的强一致性，mnode 副本之间通过同步方式进行数据复制，保证了元数据的强一致性。
+TDengine cluster is managed by mnode. To make sure the high availability of mnode, multiple replicas can be configured by system parameter `numOfMnodes`. The data replication between mnode replicas is in synchronous way to guarantee the metadata consistency.
 
-TDengine 集群中的时序数据的副本数是与数据库关联的，一个集群里可以有多个数据库，每个数据库可以配置不同的副本数。创建数据库时，通过参数 replica 指定副本数。为了支持高可靠，需要设置副本数大于 1。
+The number of replicas for time series data in TDengine is associated with each database, there can be a lot of databases in a cluster while each database can be configured with a different number of replicas. When creating a database, parameter `replica` is used to configure the number of replications. To achieve high availability, `replica` needs to be higher than 1.
 
-TDengine 集群的节点数必须大于等于副本数，否则创建表时将报错。
+The number of dnodes in a TDengine cluster must NOT be lower than the number of replicas for any database, otherwise it would fail when trying to create table.集
 
-当 TDengine 集群中的节点部署在不同的物理机上，并设置多个副本数时，就实现了系统的高可靠性，无需再使用其他软件或工具。TDengine 企业版还可以将副本部署在不同机房，从而实现异地容灾。
+As long as the dnodes of a TDengine cluster are deployed on different physical machines and replica number is set to bigger than 1, high availability can be achieved without any other assistance. If dnodes of TDengine cluster are deployed in geographically different data centers, disaster recovery can be achieved too.

docs-en/13-operation/06-admin.md

 ---
-title: 用户管理
+title: User Management
 ---
 
-系统管理员可以在 CLI 界面里添加、删除用户，也可以修改密码。CLI 里 SQL 语法如下：
+System operator can use TDengine CLI `taos` to create or remove user or change password. The SQL command is as low:
+
+## Create User
 
 ```sql
 CREATE USER <user_name> PASS <'password'>;
 ```
 
-创建用户，并指定用户名和密码，密码需要用单引号引起来，单引号为英文半角
+When creating a user and specifying the user name and password, password needs to be quoted using single quotes.
+
+## Drop User
 
 ```sql
 DROP USER <user_name>;
 ```
 
-删除用户，限 root 用户使用
+Drop a user can only be performed by root.
+
+## Change Password
 
 ```sql
 ALTER USER <user_name> PASS <'password'>;
 ```
 
-修改用户密码，为避免被转换为小写，密码需要用单引号引用，单引号为英文半角
+To keep the case of the password when changing password, password needs to be quoted using single quotes.
+
+## Change Privilege
 
 ```sql
 ALTER USER <user_name> PRIVILEGE <write|read>;
 ```
 
-修改用户权限为：write 或 read，不需要添加单引号
+The privileges that can be changed to are `read` or `write` without single quotes.
+
+Note：there is another privilege `super`, which not allowed to be authorized to any user.
 
-说明：系统内共有 super/write/read 三种权限级别，但目前不允许通过 alter 指令把 super 权限赋予用户。
+## Show Users
 
 ```sql
 SHOW USERS;
 ```
 
-显示所有用户
-
 :::note
-SQL 语法中，< >表示需要用户输入的部分，但请不要输入< >本身。
+In SQL syntax, `< >` means the part that needs to be input by user, excluding the `< >` itself.
 
 :::

docs-en/13-operation/07-import.md

 ---
-title: 数据导入
+sidebar_label: Import
+title: Import Data
 ---
 
-TDengine 提供多种方便的数据导入功能，一种按脚本文件导入，一种按数据文件导入，一种是 taosdump 工具导入本身导出的文件。
+There are multiple ways of importing data provided byTDengine: import with script, import from data file, import using `taosdump`.
 
-## 按脚本文件导入
+## Import Using Script
 
-TDengine 的 shell 支持 source filename 命令，用于批量运行文件中的 SQL 语句。用户可将建库、建表、写数据等 SQL 命令写在同一个文件中，每条命令单独一行，在 shell 中运行 source 命令，即可按顺序批量运行文件中的 SQL 语句。以‘#’开头的 SQL 语句被认为是注释，shell 将自动忽略。
+TDengine CLI `taos` supports `source <filename>` command for executing the SQL statements in the file in batch. The SQL statements for creating databases, creating tables, and inserting rows can be written in single file with one statement on each line, then the file can be executed using `source` command in TDengine CLI `taos` to execute the SQL statements in order and in batch. In the script file, any line beginning with "#" is treated as comments and ignored silently.
 
-## 按数据文件导入
+## Import from Data File
 
-TDengine 也支持在 shell 对已存在的表从 CSV 文件中进行数据导入。CSV 文件只属于一张表且 CSV 文件中的数据格式需与要导入表的结构相同，在导入的时候，其语法如下：
+In TDengine CLI, data can be imported from a CSV file into an existing table. The data in single CSV must belong to same table and must be consistent with the schema of that table. The SQL statement is as below:也
 
 ```sql
 insert into tb1 file 'path/data.csv';
 ```
 
 :::note
-注意：如果 CSV 文件首行存在描述信息，请手动删除后再导入。如某列为空，填 NULL，无引号。\*\*
+If there is description in the first line of a CSV file, please remove it before importing. If there is no value for a column, please use `NULL` without quotes.
 
 :::
 
-例如，现在存在一个子表 d1001, 其表结构如下：
+For example, there is a sub table d1001 whose schema is as below:
 
 ```sql
 taos> DESCRIBE d1001
@@ -35,7 +36,7 @@ taos> DESCRIBE d1001
  groupid                        | INT                |           4 | TAG        |
 ```
 
-要导入的 data.csv 的格式如下：
+The format of the CSV file to be imported, data.csv, is as below:
 
 ```csv
 '2018-10-04 06:38:05.000',10.30000,219,0.31000
@@ -49,13 +50,13 @@ taos> DESCRIBE d1001
 '2018-10-12 06:38:05.000',18.30000,219,0.31000
 ```
 
-那么可以用如下命令导入数据：
+Then, below SQL statement can be used to import data from file "data.csv", assuming the file is located under the home directory of current Linux user.
 
 ```sql
 taos> insert into d1001 file '~/data.csv';
 Query OK, 9 row(s) affected (0.004763s)
 ```
 
-## taosdump 工具导入
+## Import using taosdump
 
-TDengine 提供了方便的数据库导入导出工具 taosdump。用户可以将 taosdump 从一个系统导出的数据，导入到其他系统中。具体使用方法，请参见：[TDengine 数据备份工具: taosdump](/reference/taosdump)。
+A convenient tool for importing and exporting data is provided by TDengine, `taosdump`, which can used to export data from one TDengine cluster and import into another one. For the details of using `taosdump` please refer to [Tool for exporting and importing data: taosdump](/reference/taosdump).

docs-en/13-operation/08-export.md

 ---
-title: 数据导出
+sidebar_label: Export
+title: Export Data
 ---
 
-为方便数据导出，TDengine 提供了两种导出方式，分别是按表导出和用 taosdump 导出。
+There are two ways of exporting data from a TDengine cluster, one is SQL statement in TDengine CLI, the other one is `taosdump`.
 
-## 按表导出 CSV 文件
+## Export Using SQL
 
-如果用户需要导出一个表或一个 STable 中的数据，可在 taos shell 中运行：
+If you want to export the data of a table or a stable, please execute below SQL statement in TDengine CLI.
 
 ```sql
 select * from <tb_name> >> data.csv;
 ```
 
-这样，表 tb_name 中的数据就会按照 CSV 格式导出到文件 data.csv 中。
+The data of table or stable specified by `tb_name` will be exported into a file named `data.csv` in CSV format.
 
-## 用 taosdump 导出数据
+## Export Using taosdump
 
-利用 taosdump，用户可以根据需要选择导出所有数据库、一个数据库或者数据库中的一张表，所有数据或一时间段的数据，甚至仅仅表的定义。具体使用方法，请参见：
-[TDengine 数据备份工具: taosdump](/reference/taosdump)。
+With `taosdump`, you can choose to export the data of all databases, a database, a table or a stable, you can also choose export the data within a time range, or even only export the schema definition of a table. For the details of using `taosdump` please refer to [Tool for exporting and importing data: taosdump](/reference/taosdump).

docs-en/13-operation/09-status.md

 ---
-title: 系统连接、任务查询管理
+sidebar_label: Connections & Tasks
+title: Manage Connections and Query Tasks
 ---
 
-系统管理员可以从 CLI 查询系统的连接、正在进行的查询、流式计算，并且可以关闭连接、停止正在进行的查询和流式计算。
+System operator can use TDengine CLI to show the connections, ongoing queries, stream computing, and can close connection or stop ongoing query task or stream computing.
 
-## 显示数据库的连接
+## Show Connections
 
 ```sql
 SHOW CONNECTIONS;
 ```
 
-其结果中的一列显示 ip:port, 为连接的 IP 地址和端口号。
+One column of the output of the above SQL command is "ip:port", which is the end point of the client.
 
-## 强制关闭数据库连接
+## Close Connections Forcedly
 
 ```sql
 KILL CONNECTION <connection-id>;
 ```
 
-其中的 connection-id 是 SHOW CONNECTIONS 中显示的第一列的数字。
+In the above SQL command, `connection-id` is from the first column of the output of `SHOW CONNECTIONS`.
 
-## 显示数据查询
+## Show Ongoing Queries
 
 ```sql
 SHOW QUERIES;
 ```
 
-其中第一列显示的以冒号隔开的两个数字为 query-id，为发起该 query 应用连接的 connection-id 和查询次数。
+The first column of the output is query ID, which is composed of the corresponding connection ID and the sequence number of the current query task started on this connection, in format of "connection-id:query-no".
 
-## 强制关闭数据查询
+## Close Queries Forcedly
 
 ```sql
 KILL QUERY <query-id>;
 ```
 
-其中 query-id 是 SHOW QUERIES 中显示的 connection-id:query-no 字串，如“105:2”，拷贝粘贴即可。
+In the above SQL command, `query-id` is from the first column of the output of `SHOW QUERIES `.
 
-## 显示连续查询
+## Show Continuous Query
 
 ```sql
 SHOW STREAMS;
 ```
 
-其中第一列显示的以冒号隔开的两个数字为 stream-id, 为启动该 stream 应用连接的 connection-id 和发起 stream 的次数。
+The first column of the output is stream ID, which is composed of the connection ID and the sequence number of the current stream started on this connection, in the format of "connection-id:stream-no".
 
-## 强制关闭连续查询
+## Close Continuous Query Forcedly
 
 ```sql
 KILL STREAM <stream-id>;
 ```
 
-其中的 stream-id 是 SHOW STREAMS 中显示的 connection-id:stream-no 字串，如 103:2，拷贝粘贴即可。
+The the above SQL command, `stream-id` is from the first column of the output of `SHOW STREAMS`.

docs-en/13-operation/10-monitor.md

 ---
-title: 系统监控
+sidebar_label: Monitor
+title: Monitor TDengine
 ---
 
-TDengine 启动后，会自动创建一个监测数据库 log，并自动将服务器的 CPU、内存、硬盘空间、带宽、请求数、磁盘读写速度、慢查询等信息定时写入该数据库。TDengine 还将重要的系统操作（比如登录、创建、删除数据库等）日志以及各种错误报警信息记录下来存放在 log 库里。系统管理员可以从 CLI 直接查看这个数据库，也可以在 WEB 通过图形化界面查看这些监测信息。
+After TDengine is started, a database named `log` for monitoring is created automatically. The information about CPU, memory, disk, bandwidth, number of requests, disk I/O speed, slow query is written into `log` database on the basis of a predefined interval. Besides, some important system operations, like logon, create user, drop database, and alerts and warnings generated in TDengine are written into `log` database too. System operator can view the data in `log` database from TDengine CLI or from a web console.
 
-这些监测信息的采集缺省是打开的，但可以修改配置文件里的选项 monitor 将其关闭或打开。
+Collection of the monitoring information is enabled by default, but can be disabled by parameter `monitor` in configuration file. 
 
-## TDinsight - 使用监控数据库 + Grafana 对 TDengine 进行监控的解决方案
+## TDinsight 
 
-从 2.3.3.0 开始，监控数据库将提供更多的监控项，您可以从 [TDinsight Grafana Dashboard](https://grafana.com/grafana/dashboards/15167) 了解如何使用 TDinsight 方案对 TDengine 进行监控。
+TDinsight is a total solution which uses the monitor database `log` mentioned previously and Grafana to monitor a TDengine cluster.
 
-我们提供了一个自动化脚本 `TDinsight.sh` 对 TDinsight 进行部署。
+From version 2.3.3.0, more monitoring data has been added in the `log` database. Please refer to [TDinsight Grafana Dashboard](https://grafana.com/grafana/dashboards/15167) to learn more details about using TDinsight to monitor TDengine.
 
-下载 `TDinsight.sh`：
+A script `TDinsight.sh` is provided to deploy TDinsight in automatic way.
+
+Download `TDinsight.sh` with below command:
 
 ```bash
 wget https://github.com/taosdata/grafanaplugin/raw/master/dashboards/TDinsight.sh
 chmod +x TDinsight.sh
 ```
 
-准备：
+Prepare：
+
+1. TDengine Server
 
-1. TDengine Server 信息：
+   - The URL of REST service：for example `http://localhost:6041` if TDengine is deployed locally
+   - User name and password
 
-   - TDengine RESTful 服务：对本地而言，可以是 `http://localhost:6041`，使用参数 `-a`。
-   - TDengine 用户名和密码，使用 `-u` `-p` 参数设置。
+2. Grafana Alert Notification
 
-2. Grafana 告警通知
+There are two ways to setup Grafana alert notification.
 
-   - 使用已经存在的 Grafana Notification Channel `uid`，参数 `-E`。该参数可以使用 `curl -u admin:admin localhost:3000/api/alert-notifications |jq` 来获取。
+- An existing Grafana Notification Channel can be specified with parameter `-E`, the notifier uid of the channel can be obtained by `curl -u admin:admin localhost:3000/api/alert-notifications |jq`
 
      ```bash
      sudo ./TDinsight.sh -a http://localhost:6041 -u root -p taosdata -E <notifier uid>
      ```
 
-   - 使用 TDengine 数据源插件内置的阿里云短信告警通知，使用 `-s` 启用之，并设置如下参数：
+- The AliClund SMS alert built in TDengine data source plugin can be enabled with parameter `-s`, the parameters of this way are as follows:
+
+  - `-I`: AliCloud SMS Key ID
+  - `-K`: AliCloud SMS Key Secret
+  - `-S`: AliCloud SMS Signature
+  - `-C`: SMS notification template
+  - `-T`: Input parameters in JSON format for the SMS notification template, for example`{"alarm_level":"%s","time":"%s","name":"%s","content":"%s"}`
+  - `-B`: List of mobile numbers to be notified
 
-     1. 阿里云短信服务 Key ID，参数 `-I`
-     2. 阿里云短信服务 Key Secret，参数 `K`
-     3. 阿里云短信服务签名，参数 `-S`
-     4. 短信通知模板号，参数 `-C`
-     5. 短信通知模板输入参数，JSON 格式，参数 `-T`，如 `{"alarm_level":"%s","time":"%s","name":"%s","content":"%s"}`
-     6. 逗号分隔的通知手机列表，参数 `-B`
+  Below is an example of the full command using this way.
 
   ```bash
      sudo ./TDinsight.sh -a http://localhost:6041 -u root -p taosdata -s \
@@ -49,6 +56,6 @@ chmod +x TDinsight.sh
        -T '{"alarm_level":"%s","time":"%s","name":"%s","content":"%s"}'
   ```
 
-运行程序并重启 Grafana 服务，打开面板：`http://localhost:3000/d/tdinsight`。
+Launch `TDinsight.sh` as above command and restart Grafana, then open Dashboard `http://localhost:3000/d/tdinsight`.
 
-更多使用场景和限制请参考[TDinsight](/reference/tdinsight/) 文档。
+For more use cases and restrictions please refer to [TDinsight](/reference/tdinsight/).

docs-en/13-operation/17-diagnose.md

 ---
-title: 诊断及其他
+sidebar_label: Diagnose
+title: Diagnose Problems
 ---
 
-## 网络连接诊断
+## Diagnose Network Connection
 
-当出现客户端应用无法访问服务端时，需要确认客户端与服务端之间网络的各端口连通情况，以便有针对性地排除故障。
+When the client is unable to access the server, the network connection between the client side and the server side needs to be checked to find out the root cause and resolve problems.
 
-目前网络连接诊断支持在：Linux 与 Linux，Linux 与 Windows 之间进行诊断测试。
+The diagnostic for network connection can be executed between Linux and Linux or between Linux and Windows.
 
-诊断步骤：
+Diagnostic steps：
 
-1. 如拟诊断的端口范围与服务器 taosd 实例的端口范围相同，须先停掉 taosd 实例
-2. 服务端命令行输入：`taos -n server -P <port> -l <pktlen>` 以服务端身份启动对端口 port 为基准端口的监听
-3. 客户端命令行输入：`taos -n client -h <fqdn of server> -P <port> -l <pktlen>` 以客户端身份启动对指定的服务器、指定的端口发送测试包
+1. If the port range to be diagnosed are being occupied by a `taosd` server process, please firstly stop `taosd.
+2. On the server side, execute command `taos -n server -P <port> -l <pktlen>` to monitor the port range starting from the port specified by `-P` parameter with the role of "server.
+3. On the client side, execute command `taos -n client -h <fqdn of server> -P <port> -l <pktlen>` to send testing package to the specified server and port.
  
--l <pktlen\>： 测试网络包的大小（单位：字节）。最小值是 11、最大值是 64000，默认值为 1000。
-注：两端命令行中指定的测试包长度必须一致，否则测试显示失败。
+-l <pktlen\>： The size of the testing package, in bytes. The value range is [11, 64,000] and default value is 1,000. Please be noted that the package length must be same in the above 2 commands executed on server side and client side respectively.
 
-服务端运行正常的话会输出以下信息：
+Output of the server side is as below for example:
 
 ```bash
 # taos -n server -P 6000
@@ -48,7 +48,7 @@ title: 诊断及其他
 12/21 14:50:22.721261 0x7f53427ec700 UTL UDP: send:1000 bytes to 172.27.0.8 at 6011
 ```
 
-客户端运行正常会输出以下信息：
+Output of the client side is as below for example:
 
 ```bash
 # taos -n client -h 172.27.0.7 -P 6000
@@ -66,66 +66,58 @@ title: 诊断及其他
 12/21 14:50:22.721274 0x7fc95d859200 UTL successed to test UDP port:6011
 ```
 
-仔细阅读打印出来的错误信息，可以帮助管理员找到原因，以解决问题。
+The output needs to be checked carefully for the system operator to find out root cause and solve the problem.
 
-## 启动状态及 RPC 诊断
+## Startup Status and RPC Diagnostic
 
-`taos -n startup -h <fqdn of server>`
+`taos -n startup -h <fqdn of server>` can be used to check the startup status of a `taosd` process. This is a comman task for a system operator to do to determine whether `taosd` has been started successfully, especially in case of cluster.
 
-判断 taosd 服务端是否成功启动，是数据库管理员经常遇到的一种情形。特别当若干台服务器组成集群时，判断每个服务端实例是否成功启动就会是一个重要问题。除检索 taosd 服务端日志文件进行问题定位、分析外，还可以通过 `taos -n startup -h <fqdn of server>` 来诊断一个 taosd 进程的启动状态。
+`taos -n rpc -h <fqdn of server>` can be used to check whether the port of a started `taosd` can be accessed or not. If `taosd` process doesn't respond or work abnormally, this command can be used to initiate a rpc communication with the specified fqdn to determine whether it's network problem or `taosd` is abnormal.
 
-针对多台服务器组成的集群，当服务启动过程耗时较长时，可通过该命令行来诊断每台服务器的 taosd 实例的启动状态，以准确定位问题。
+## Sync and Arbitrator Diagnostic
 
-`taos -n rpc -h <fqdn of server>`
-
-该命令用来诊断已经启动的 taosd 实例的端口是否可正常访问。如果 taosd 程序异常或者失去响应，可以通过 `taos -n rpc -h <fqdn of server>` 来发起一个与指定 fqdn 的 rpc 通信，看看 taosd 是否能收到，以此来判定是网络问题还是 taosd 程序异常问题。
-
-## sync 及 arbitrator 诊断
-
-```
+```bash
 taos -n sync -P 6040 -h <fqdn of server>
 taos -n sync -P 6042 -h <fqdn of server>
 ```
 
-用来诊断 sync 端口是否工作正常，判断服务端 sync 模块是否成功工作。另外，-P 6042 用来诊断 arbitrator 是否配置正常，判断指定服务器的 arbitrator 是否能正常工作。
+The above commands can be executed on Linux Shell to check whether the port for sync works well and whether the sync module of the server side works well. Besides, `-P 6042` is used to check whether the arbitrator is configured properly and works well.
 
-## 网络速度诊断
+## Network Speed Diagnostic
 
 `taos -n speed -h <fqdn of server> -P 6030 -N 10 -l 10000000 -S TCP`
 
-从 2.2.0.0 版本开始，taos 工具新提供了一个网络速度诊断的模式，可以对一个正在运行中的 taosd 实例或者 `taos -n server` 方式模拟的一个服务端实例，以非压缩传输的方式进行网络测速。这个模式下可供调整的参数如下：
+From version 2.2.0.0, the above command can be executed on Linux Shell to test the network speed, it sends uncompressed package to a running `taosd` server process or a simulated server process started by `taos -n server` to test the network speed. Parameters can be used when testing network speed are as below:
 
--n：设为“speed”时，表示对网络速度进行诊断。
--h：所要连接的服务端的 FQDN 或 ip 地址。如果不设置这一项，会使用本机 taos.cfg 文件中 FQDN 参数的设置作为默认值。
--P：所连接服务端的网络端口。默认值为 6030。
--N：诊断过程中使用的网络包总数。最小值是 1、最大值是 10000，默认值为 100。
--l：单个网络包的大小（单位：字节）。最小值是 1024、最大值是 1024 `*` 1024 `*` 1024，默认值为 1024。
--S：网络封包的类型。可以是 TCP 或 UDP，默认值为 TCP。
+-n：When set to "speed", it means testing network speed
+-h：The FQDN or IP of the server process to be connected to; if not set, the FQDN configured in `taos.cfg` is used
+-P：The port of the server process to connect to, the default value is 6030
+-N：The number of packages that will be sent in the test, range is [1,10000], default value is 100
+-l：The size of each package in bytes, range is [1024, 1024 \* 1024 \* 1024], default value is 1024
+-S：The type of network packages to send, can be either TCP or UDP, default value is 
 
-## FQDN 解析速度诊断
+## FQDN Resolution Diagnostic
 
 `taos -n fqdn -h <fqdn of server>`
 
-从 2.2.0.0 版本开始，taos 工具新提供了一个 FQDN 解析速度的诊断模式，可以对一个目标 FQDN 地址尝试解析，并记录解析过程中所消耗的时间。这个模式下可供调整的参数如下：
-
--n：设为“fqdn”时，表示对 FQDN 解析进行诊断。
--h：所要解析的目标 FQDN 地址。如果不设置这一项，会使用本机 taos.cfg 文件中 FQDN 参数的设置作为默认值。
+From version 2.2.0.0, the above command can be executed on Linux Shell to test the resolution speed of FQDN. It can be used to try to resolve a FQDN to an IP address and record the time spent in this process. The parameters that can be used for this purpose are as below:
 
-## 服务端日志
+-n：When set to "fqdn", it means testing the speed of resolving FQDN
+-h：The FQDN to be resolved. If not set, the `FQDN` parameter in `taos.cfg` is used by default.
 
-taosd 服务端日志文件标志位 debugflag 默认为 131，在 debug 时往往需要将其提升到 135 或 143 。
+## Server Log
 
-一旦设定为 135 或 143，日志文件增长很快，特别是写入、查询请求量较大时，增长速度惊人。如合并保存日志，很容易把日志内的关键信息（如配置信息、错误信息等）冲掉。为此，服务端将重要信息日志与其他日志分开存放：
+The parameter `debugFlag` is used to control the log level of `taosd` server process. The default value is 131, for debug purpose it needs to be escalated to 135 or 143. 
 
-- taosinfo 存放重要信息日志, 包括：INFO/ERROR/WARNING 级别的日志信息。不记录 DEBUG、TRACE 级别的日志。
-- taosdlog 服务器端生成的日志，记录 taosinfo 中全部信息外，还根据设置的日志输出级别，记录 DEBUG（日志级别 135）、TRACE（日志级别是 143）。
+Once this parameter is set to 135 or 143, the log file grows very quickly especially when there is huge volume of data insertion and data query requests. If all the logs are stored together, some important information may be missed very easily, so on server side important information is stored at different place from other logs.一
 
-## 客户端日志
+- The log at level of INFO, WARNING and ERROR is stored in `taosinfo` so that it is easy to find important information 
+- The log at level of DEBUG (135) and TRACE (143) and other information not handled by `taosinfo` are stored in `taosdlog`
 
-每个独立运行的客户端（一个进程）生成一个独立的客户端日志，其命名方式采用 taoslog+<序号> 的方式命名。文件标志位 debugflag 默认为 131，在 debug 时往往需要将其提升到 135 或 143 。
+## Client Log
 
-- taoslog 客户端（driver）生成的日志，默认记录客户端 INFO/ERROR/WARNING 级别日志，还根据设置的日志输出级别，记录 DEBUG（日志级别 135）、TRACE（日志级别是 143）。
+An independent log file, named as "taoslog+<seq num\>" is generated for each client program, i.e. a client process. The default value of `debugfalg` is also 131 and only log at level of INFO/ERROR/WARNING is recorded, it and needs to be changed to 135 or 143 so that log at DEBUG or TRACE level can be recorded for debugging purpose.
 
-其中，日志文件最大长度由 numOfLogLines 来进行配置，一个 taosd 实例最多保留两个文件。
+The maximum length of a single log file is controlled by parameter `numOfLogLines` and only 2 log files are kept for each `taosd` server process.
 
-taosd 服务端日志采用异步落盘写入机制，优点是可以避免硬盘写入压力太大，对性能造成很大影响。缺点是，在极端情况下，存在少量日志行数丢失的可能。
+log file is written in async way to minimize the workload on disk, bu the penalty is that a few log lines may be lost in some extreme conditions.