Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Binary file added src/.vuepress/public/img/sha512-02.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added src/.vuepress/public/img/sha512-03.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added src/.vuepress/public/img/sha512-04.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added src/.vuepress/public/img/sha512-05.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added src/.vuepress/public/img/sha512-06.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added src/.vuepress/public/img/sha512-07.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added src/.vuepress/public/img/sha512-08.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Original file line number Diff line number Diff line change
Expand Up @@ -52,7 +52,37 @@ Unzip and install the package
| README_ZH.md | file | Explanation of the Chinese version of the markdown format |
| README.md | file | Instructions |

### 2.2 Environmental Preparation

### 2.2 Pre-installation Check

To ensure the AINode installation package you obtained is complete and valid, we recommend performing an SHA512 verification before proceeding with the installation and deployment.

#### Preparation:

- Obtain the officially released SHA512 checksum: Visit the [Release Versions](https://iotdb.apache.org/zh/Download/) page on the IoTDB open-source official website to get it.

#### Verification Steps (Linux as an Example):

1. Open the terminal and navigate to the directory where the installation package is stored (e.g., /data/ainode):
```Bash
cd /data/ainode
```
2. Execute the following command to calculate the hash value:
```Bash
sha512sum timechodb-{version}-ainode-bin.zip
```
3. The terminal will output a result (the left part is the SHA512 checksum, and the right part is the file name):

![img](/img/sha512-06.png)

4. Compare the output result with the official SHA512 checksum. Once confirmed that they match, you can proceed with the installation and deployment of AINode as per the procedures below.

#### Notes:

- If the verification results do not match, please re-obtain the installation package.
- If a "file not found" prompt appears during verification, check whether the file path is correct or if the installation package has been fully downloaded.

### 2.3 Environmental Preparation

1. Recommended operating systems: Ubuntu, MacOS
2. IoTDB version: >= V 2.0.5.1
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -52,7 +52,36 @@ Unzip and install the package
| README_ZH.md | file | Explanation of the Chinese version of the markdown format |
| README.md | file | Instructions |

### 2.2 Environmental Preparation
### 2.2 Pre-installation Check

To ensure the AINode installation package you obtained is complete and valid, we recommend performing an SHA512 verification before proceeding with the installation and deployment.

#### Preparation:

- Obtain the officially released SHA512 checksum:please contact Timecho Team to re-obtain the installation package.

#### Verification Steps (Linux as an Example):

1. Open the terminal and navigate to the directory where the installation package is stored (e.g., /data/ainode):
```Bash
cd /data/ainode
```
2. Execute the following command to calculate the hash value:
```Bash
sha512sum timechodb-{version}-ainode-bin.zip
```
3. The terminal will output a result (the left part is the SHA512 checksum, and the right part is the file name):

![img](/img/sha512-06.png)

4. Compare the output result with the official SHA512 checksum. Once confirmed that they match, you can proceed with the installation and deployment of AINode as per the procedures below.

#### Notes:

- If the verification results do not match, please contact Timecho Team to re-obtain the installation package.
- If a "file not found" prompt appears during verification, check whether the file path is correct or if the installation package has been fully downloaded.

### 2.3 Environmental Preparation

1. Recommended operating systems: Ubuntu, MacOS
2. IoTDB version: >= V 2.0.5.1
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -58,6 +58,38 @@ Use the hostname for `cn_internal_address` and `dn_internal_address` in IoTDB co
2. Configure the operating system environment according to environmental requirements (system environment configuration can be found in:[Environment Requirement](../Deployment-and-Maintenance/Environment-Requirements.md))


### 2.1 Pre-installation Check

To ensure the IoTDB installation package you obtained is complete and valid, we recommend performing an SHA512 verification before proceeding with the installation and deployment.

#### Preparation:

- Obtain the officially released SHA512 checksum: Visit the [Release Versions](https://iotdb.apache.org/zh/Download/) page on the IoTDB open-source official website to get it.

#### Verification Steps (Linux as an Example):

1. Open the terminal and navigate to the directory where the installation package is stored (e.g., /data/iotdb):
```Bash
cd /data/iotdb
```
2. Execute the following command to calculate the hash value:
```Bash
sha512sum apache-iotdb-{version}-all-bin.zip
```
3. The terminal will output a result (the left part is the SHA512 checksum, and the right part is the file name):


![img](/img/sha512-07.png)

4. Compare the output result with the official SHA512 checksum. Once confirmed that they match, you can proceed with the installation and deployment of IoTDB as per the procedures below.


#### Notes:

- If the verification results do not match, please re-obtain the installation package.
- If a "file not found" prompt appears during verification, check whether the file path is correct or if the installation package has been fully downloaded.


## 3. Installation Steps

Taking a cluster with three Linux servers with the following information as example:
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -77,7 +77,7 @@ To ensure the IoTDB Enterprise Edition installation package you obtained is comp
```
3. The terminal will output a result (the left part is the SHA512 checksum, and the right part is the file name):

![img](/img/sha512-01.png)
![img](/img/sha512-02.png)

4. Compare the output result with the official SHA512 checksum. Once confirmed that they match, you can proceed with the installation and deployment operations in accordance with the procedures below.

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -48,7 +48,39 @@ Use the hostname for `cn_internal_address` and `dn_internal_address` in IoTDB co

## 2. Installation Steps

### 2.1 Extract Installation Package
### 2.1 Pre-installation Check

To ensure the IoTDB installation package you obtained is complete and valid, we recommend performing an SHA512 verification before proceeding with the installation and deployment.

#### Preparation:

- Obtain the officially released SHA512 checksum: Visit the [Release Versions](https://iotdb.apache.org/zh/Download/) page on the IoTDB open-source official website to get it.

#### Verification Steps (Linux as an Example):

1. Open the terminal and navigate to the directory where the installation package is stored (e.g., /data/iotdb):
```Bash
cd /data/iotdb
```
2. Execute the following command to calculate the hash value:
```Bash
sha512sum apache-iotdb-{version}-all-bin.zip
```
3. The terminal will output a result (the left part is the SHA512 checksum, and the right part is the file name):


![img](/img/sha512-07.png)

4. Compare the output result with the official SHA512 checksum. Once confirmed that they match, you can proceed with the installation and deployment of IoTDB as per the procedures below.


#### Notes:

- If the verification results do not match, please re-obtain the installation package.
- If a "file not found" prompt appears during verification, check whether the file path is correct or if the installation package has been fully downloaded.


### 2.2 Extract Installation Package

Unzip the installation package and navigate to the directory:

Expand All @@ -57,9 +89,9 @@ unzip apache-iotdb-{version}-all-bin.zip
cd apache-iotdb-{version}-all-bin
```

### 2.2 Parameters Configuration
### 2.3 Parameters Configuration

#### 2.2.1 Memory Configuration
#### 2.3.1 Memory Configuration

Edit the following files for memory allocation:

Expand All @@ -70,7 +102,7 @@ Edit the following files for memory allocation:
| :------------ | :---------------------------------- | :---------- | :-------------- | :---------------------- |
| MEMORY_SIZE | Total memory allocated for the node | Empty | As needed | Save changes without immediate execution; modifications take effect after service restart. |

#### 2.2.2 General Configuration
#### 2.3.2 General Configuration

Set the following parameters in `conf/iotdb-system.properties`. Refer to `conf/iotdb-system.properties.template` for a complete list.

Expand Down Expand Up @@ -105,7 +137,7 @@ Set the following parameters in `conf/iotdb-system.properties`. Refer to `conf/i
| dn_schema_region_consensus_port | Port used for metadata replica consensus protocol communication | 10760 | 10760 | This parameter cannot be modified after the first startup. |
| dn_seed_config_node | Address of the ConfigNode for registering and joining the cluster. (e.g.,`cn_internal_address:cn_internal_port`) | 127.0.0.1:10710 | Use `cn_internal_address:cn_internal_port` | This parameter cannot be modified after the first startup. |

### 2.3 Start ConfigNode
### 2.4 Start ConfigNode

Navigate to the `sbin` directory and start ConfigNode:

Expand All @@ -117,15 +149,15 @@ If the startup fails, refer to the [Common Issues](#3-common-issues)。 section



### 2.4 Start DataNode
### 2.5 Start DataNode

Navigate to the `sbin` directory of IoTDB and start the DataNode:

```Bash
./sbin/start-datanode.sh -d # The "-d" flag starts the process in the background.
```

### 3.5 Start CLI
### 2.6 Start CLI

Enter the IoTDB CLI.

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -68,7 +68,7 @@ To ensure the IoTDB Enterprise Edition installation package you obtained is comp
```
3. The terminal will output a result (the left part is the SHA512 checksum, and the right part is the file name):

![img](/img/sha512-01.png)
![img](/img/sha512-02.png)

4. Compare the output result with the official SHA512 checksum. Once confirmed that they match, you can proceed with the installation and deployment operations in accordance with the procedures below.

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -482,21 +482,23 @@ Key updates:

## 2. Workbench (Console Tool)

| Version | Description | Supported IoTDB Versions |
|---------|-----------------------------------------------------------------------------------------------------------------------------|-------------------------------------|
| V2.0.1-beta | The first version of the V2.x series, supporting dual models of tree and table | V2.0 and above |
| V1.5.7 | Optimize the point list by splitting point names into device names and points, ensure the point selection area supports horizontal scrolling, and align the export file column order with the page display. | All 1.x versions from V1.3.4 onward |
| V1.5.6 | Enhanced CSV import/export: optional tags/aliases on import; support for measurement descriptions with backtick-quoted quotes on export. | All 1.x versions from V1.3.4 onward |
| V1.5.5 | Added server clock functionality and support for activating Enterprise Edition license databases | All 1.x versions from V1.3.4 onward |
| V1.5.4 | Added authentication for Prometheus settings in Instance Management | All 1.x versions from V1.3.4 onward |
| V1.5.1 | Added AI analysis and pattern matching | All 1.x versions from V1.3.2 onward |
| V1.4.0 | Added tree model display and English UI | All 1.x versions from V1.3.2 onward |
| V1.3.1 | Enhanced analysis methods and import templates | All 1.x versions from V1.3.2 onward |
| V1.3.0 | Added DB configuration and UI refinements | All 1.x versions from V1.3.2 onward |
| V1.2.6 | Optimized permission controls | All 1.x versions from V1.3.1 onward |
| V1.2.5 | Added "Common Templates" and caching | All 1.x versions from V1.3.0 onward |
| V1.2.4 | Added import/export for calculations, time alignment field | All 1.x versions from V1.2.2 onward |
| V1.2.3 | Added activation details and analysis features | All 1.x versions from V1.2.2 onward |
| V1.2.2 | Optimized point description display | All 1.x versions from V1.2.2 onward |
| V1.2.1 | Added sync monitoring panel, Prometheus hints | All 1.x versions from V1.2.2 onward |
| V1.2.0 | Major Workbench upgrade | All 1.x versions from V1.2.0 onward |

| **Version** | **Description** | **Supported IoTDB Versions** | **SHA512 checksum** |
| ----------- | ------------------------------------------------------------ | ----------------------------------- | ------------------------------------------------------------ |
| V2.1.1 | Optimize the measuring point selection on the trend interface to support scenarios without devices | V2.0 and above | aa05fd4d9f33f07c0949bc2d6546bb4b9791ed5ea94bcef27e2bf51ea141ec0206f1c12466aced7bf3449e11ad68d65378d697f3d10cb4881024a83746029a65 |
| V2.0.1-beta | The first version of the V2.x series, supporting dual models of tree and table | V2.0 and above | 0ca0d5029874ed8ada9c7d1cb562370b3a46913eed66d39c08759287ccc8bf332cf80bb8861e788614b61ae5d53a9f5605f553e1a607e856f395eb5102e7cc4d |
| V1.5.7 | Optimize the point list by splitting point names into device names and points, ensure the point selection area supports horizontal scrolling, and align the export file column order with the page display. | All 1.x versions from V1.3.4 onward | d3cd4a63372ca5d6217b67dddf661980c6a442b3b1564235e9ad34fc254d681febd58c2cc59c6273ffbfd8a1b003b9adb130ecfaaebe1942003b0d07427b1fcc |
| V1.5.6 | Enhanced CSV import/export: optional tags/aliases on import; support for measurement descriptions with backtick-quoted quotes on export. | All 1.x versions from V1.3.4 onward | 276ac1ea341f468bf6d29489c9109e9aa61afe2d1caaab577bc40603c6f4120efccc36b65a58a29ce6a266c21b46837aad6128f84ba5e676231ea9e6284a35e5 |
| V1.5.5 | Added server clock functionality and support for activating Enterprise Edition license databases | All 1.x versions from V1.3.4 onward | b18d01b70908d503a25866d1cc69d14e024d5b10ca6fcc536932fdbef8257c66e53204663ce3be5548479911aca238645be79dfd7ee7e65a07ab3c0f68c497f6 |
| V1.5.4 | Added authentication for Prometheus settings in Instance Management | All 1.x versions from V1.3.4 onward | adc7e13576913f9e43a9671fed02911983888da57be98ec8fbbb2593600d310f69619d32b22b569520c88e29f100d7ccae995b20eba757dbb1b2825655719335 |
| V1.5.1 | Added AI analysis and pattern matching | All 1.x versions from V1.3.2 onward | 4f2053a2a3b2b255ce195268d6cd245278f3be32ba4cf68be1552c386d78ed4424f7bdc9d8e68c6b8260b3e398c8fd23ff342439c4e88e1e777c62640d2279f9 |
| V1.4.0 | Added tree model display and English UI | All 1.x versions from V1.3.2 onward | 734077f3bb5e1719d20b319d8b554ce30718c935cb0451e02b2c9267ff770e9c2d63b958222f314f16c2e6e62bf78b643255249b574ee6f37d00e123433981e8 |
| V1.3.1 | Enhanced analysis methods and import templates | All 1.x versions from V1.3.2 onward | 134f87101cc7f159f8a22ac976ad2a3a295c5435058ee0a15160892aac46ac61dd3cfb0633b4aea9cc7415bf904d0ae65aaf77d663f027d864204d81fb34768b |
| V1.3.0 | Added DB configuration and UI refinements | All 1.x versions from V1.3.2 onward | 94a137fc5c681b211f3e076472a9c5875d59e7f0cd6d7409cb8f66bb9e4f87577a0f12dd500e2bcb99a435860c82183e4a6514b638bcb4aecfb48f184730f3f1 |
| V1.2.6 | Optimized permission controls | All 1.x versions from V1.3.1 onward | f345b7edcbe245a561cb94ec2e4f4d40731fe205f134acadf5e391e5874c5c2477d9f75f15dbaf36c3a7cb6506823ac6fbc2a0ccce484b7c4cc71ec0fbdd9901 |
| V1.2.5 | Added "Common Templates" and caching | All 1.x versions from V1.3.0 onward | 37376b6cfbef7df8496e255fc33627de01bd68f636e50b573ed3940906b6f3da1e8e8b25260262293b8589718f5a72180fa15e5823437bf6dc51ed7da0c583f7 |
| V1.2.4 | Added import/export for calculations, time alignment field | All 1.x versions from V1.2.2 onward | 061ad1add38c109c1a90b06f1ddb7797bd45e84a34a4f77154ee48b90bdc7ecccc1e25eaa53fbbc98170d99facca93e3536192dd8d10a50ce505f59923ce6186 |
| V1.2.3 | Added activation details and analysis features | All 1.x versions from V1.2.2 onward | 254f5b7451300f6f99937d27fd7a5b20847d5293f53e0eaf045ac9235c7ea011785716b800014645ed5d2161078b37e1d04f3c59589c976614fb801c4da982e1 |
| V1.2.2 | Optimized point description display | All 1.x versions from V1.2.2 onward | 062e520d010082be852d6db0e2a3aa6de594eb26aeb608da28a212726e378cd4ea30fca5e1d2c3231ebd8de29e94ca9641f1fabc1cea46acfb650c37b7681b4e |
| V1.2.1 | Added sync monitoring panel, Prometheus hints | All 1.x versions from V1.2.2 onward | 8a3bcf87982ad5004528829b121f2d3945429deb77069917a42a8c8d2e2e2a2c24a398aaa87003920eeacc0c692f1ed39eac52a696887aa085cce011f0ddd745 |
| V1.2.0 | Major Workbench upgrade | All 1.x versions from V1.2.0 onward | ea1f7d3a4c0c6476a195479e69bbd3b3a2da08b5b2bb70b0a4aba988a28b5db5a209d4e2c697eb8095dfdf130e29f61f2ddf58c5b51d002c8d4c65cfc13106b3 |
Original file line number Diff line number Diff line change
Expand Up @@ -52,7 +52,37 @@
| README_ZH.md | file | Explanation of the Chinese version of the markdown format |
| README.md | file | Instructions |

### 2.2 Environmental Preparation

### 2.2 Pre-installation Check

To ensure the AINode installation package you obtained is complete and valid, we recommend performing an SHA512 verification before proceeding with the installation and deployment.

#### Preparation:

- Obtain the officially released SHA512 checksum: Visit the [Release Versions](https://iotdb.apache.org/zh/Download/) page on the IoTDB open-source official website to get it.

#### Verification Steps (Linux as an Example):

1. Open the terminal and navigate to the directory where the installation package is stored (e.g., /data/ainode):
```Bash
cd /data/ainode
```
2. Execute the following command to calculate the hash value:
```Bash
sha512sum timechodb-{version}-ainode-bin.zip
```
3. The terminal will output a result (the left part is the SHA512 checksum, and the right part is the file name):

![img](/img/sha512-06.png)

4. Compare the output result with the official SHA512 checksum. Once confirmed that they match, you can proceed with the installation and deployment of AINode as per the procedures below.

#### Notes:

- If the verification results do not match, please re-obtain the installation package.
- If a "file not found" prompt appears during verification, check whether the file path is correct or if the installation package has been fully downloaded.

### 2.3 Environmental Preparation

1. Recommended operating systems: Ubuntu, MacOS
2. IoTDB version: >= V 2.0.5.1
Expand Down
Loading