fix title bug and add English doc by wanghui42 · Pull Request #100 · apache/iotdb-docs

wanghui42 · 2023-10-11T10:58:19Z

No description provided.

Co-authored-by: Haonan <hhaonan@outlook.com>

StefanieZhao7 · 2023-10-17T09:36:44Z

src/UserGuide/V1.2.x/User-Manual/Tiered-Storage_timecho.md

+
+In this example, two levels of storage are configured, specifically:
+
+| **层级** | **数据目录**                           | **数据范围**    | **磁盘最小剩余空间阈值** |


This part needs to be in English

StefanieZhao7 · 2023-10-17T09:37:01Z

src/UserGuide/V1.2.x/User-Manual/Tiered-Storage_timecho.md

+
+In this example, a total of three levels of storage are configured, specifically:
+
+| **层级** | **数据目录**                           | **数据范围**                 | **磁盘最小剩余空间阈值** |


This part needs to be in English

chrisdutz

Had some changes in the english texts.

chrisdutz · 2023-10-17T11:50:53Z

src/UserGuide/V1.2.x/IoTDB-Introduction/Publication.md


-## Benchmark tools
-
-We also developed Benchmark tools for time series databases 


Rather write: "benchmarking tools"

chrisdutz · 2023-10-17T12:34:09Z

src/UserGuide/V1.2.x/User-Manual/Tiered-Storage_timecho.md

+## Overview

-TODO
+Tiered storage function provides users with the ability to manage tiered storage media. users can use the tiered storage function to configure different types of storage media for IoTDB and to classify the storage media. ioTDB can support tiered storage from memory, SSD, normal hard disc to network hard disc by parameter configuration only according to the degree of hot and cold data. Specifically, in IoTDB, the configuration of tiered storage is reflected in the management of multiple directories. Users can group tiered storage directories into the same category and configure them into IoTDB as a "tier", which is called storage tier; at the same time, users can categorize data according to hot or cold, and store different categories of data into designated storage tiers. Meanwhile, users can categorise data according to hot or cold and store different categories of data in the specified tier. Currently, IoTDB supports the classification of hot and cold data by TTL, when the data in one tier does not meet the TTL rules defined in the current tier, the data will be automatically migrated to the next tier.


The Tiered storage functionality allows users to define multiple layers of storage, spanning across multiple types of storage media (Memory mapped directory, SSD, rotational hard discs or cloud storage). While memory and cloud storage is usually singular, the local file system storages can consist of multiple directories joined together into one tier. In order to decide where to store data, the probably most important configuration option is the TTL (Time to live / age) of data. Therefore for each tier a default TTL needs to be provided. Each tier also has a quota to how much data it can contain. When inserting data, IoTDB checks if the conditions for the first layer match (Is the data too old? Is the layer already saturated with too much data?) If any of the conditions don't match, the next tier is checked until a matching tier is found.

chrisdutz · 2023-10-17T12:36:43Z

src/UserGuide/V1.2.x/User-Manual/Tiered-Storage_timecho.md

+
+| Configuration                                    | Default                    | Description                                                          | Constraint                                                          |
+| ---------------------------------------- | ------------------------ | ------------------------------------------------------------ | ------------------------------------------------------------ |
+| dn_data_dirs                             | None                        | specify different storage directories and divide the storage directories into tiers             | Each level of storage uses a semicolon to separate, and commas to separate within a single level; cloud configuration can only be used as the last level of storage and the first level can't be used as cloud storage; a cloud object at most; the remote storage directory is denoted by OBJECT_STORAGE |


| dn_data_dirs | None | specify different storage directories and divide the storage directories into tiers | Each level of storage uses a semicolon to separate, and commas to separate within a single level; cloud (OBJECT_STORAGE) configuration can only be used as the last level of storage and the first level can't be used as cloud storage; a cloud object at most; the remote storage directory is denoted by OBJECT_STORAGE |

chrisdutz · 2023-10-17T12:37:32Z

src/UserGuide/V1.2.x/User-Manual/Tiered-Storage_timecho.md

+| Configuration                                    | Default                    | Description                                                          | Constraint                                                          |
+| ---------------------------------------- | ------------------------ | ------------------------------------------------------------ | ------------------------------------------------------------ |
+| dn_data_dirs                             | None                        | specify different storage directories and divide the storage directories into tiers             | Each level of storage uses a semicolon to separate, and commas to separate within a single level; cloud configuration can only be used as the last level of storage and the first level can't be used as cloud storage; a cloud object at most; the remote storage directory is denoted by OBJECT_STORAGE |
+| default_ttl_in_ms                        | None                        | Define the scope of data for which each tier is responsible, expressed through a TTL                    | Each level of storage is separated by a semicolon; the number of levels should match the number of levels defined by dn_data_dirs |


| default_ttl_in_ms | None | Define the maximum age of data for which each tier is responsible | Each level of storage is separated by a semicolon; the number of levels should match the number of levels defined by dn_data_dirs |

chrisdutz · 2023-10-17T12:38:06Z

src/UserGuide/V1.2.x/User-Manual/Tiered-Storage_timecho.md

+| object_storage_type                      | AWS_S3                   | Cloud Storage Type                                                 | IoTDB currently only supports AWS S3 as a remote storage type, and this parameter can't be modified   |
+| object_storage_bucket                    | None                        | Name of cloud storage bucket                                       | Bucket definition in AWS S3; no need to configure if remote storage is not used        |
+| object_storage_endpoiont                 |                          | endpoint of cloud storage                                          | endpoint of AWS S3；If remote storage is not used, no configuration required             |
+| object_storage_access_key                |                          | Authentication information stored in the cloud: key                                       | AWS S3 的 credential key；If remote storage is not used, no configuration required       |


| object_storage_access_key | | Authentication information stored in the cloud: key | AWS S3 credential key；If remote storage is not used, no configuration required |

chrisdutz · 2023-10-17T12:38:14Z

src/UserGuide/V1.2.x/User-Manual/Tiered-Storage_timecho.md

+| object_storage_bucket                    | None                        | Name of cloud storage bucket                                       | Bucket definition in AWS S3; no need to configure if remote storage is not used        |
+| object_storage_endpoiont                 |                          | endpoint of cloud storage                                          | endpoint of AWS S3；If remote storage is not used, no configuration required             |
+| object_storage_access_key                |                          | Authentication information stored in the cloud: key                                       | AWS S3 的 credential key；If remote storage is not used, no configuration required       |
+| object_storage_access_secret             |                          | Authentication information stored in the cloud: secret                                    | AWS S3 的 credential secret；If remote storage is not used, no configuration required    |


| object_storage_access_secret | | Authentication information stored in the cloud: secret | AWS S3 credential secret；If remote storage is not used, no configuration required |

chrisdutz · 2023-10-17T12:39:28Z

src/UserGuide/V1.2.x/User-Manual/Tiered-Storage_timecho.md

+| **tier** | **data path**                           | **data range**    | **threshold for minimum remaining disk space** |
+| -------- | -------------------------------------- | --------------- | ------------------------ |
+| tier 1   | path 1：/data1/data                    | data for last 1 day | 20%                      |
+| tier 2   | path 2：/data2/data path 2：/data3/data | data from 1 day ago  | 10%                      |


chrisdutz · 2023-10-17T12:40:12Z

src/UserGuide/V1.2.x/User-Manual/Tiered-Storage_timecho.md

+
+| **tier** | **data path**                           | **data range**                 | **threshold for minimum remaining disk space** |
+| -------- | -------------------------------------- | ---------------------------- | ------------------------ |
+| tier一   | path 1：/data1/data                    | data for last 1 day              | 20%                      |


chrisdutz · 2023-10-17T12:40:36Z

src/UserGuide/V1.2.x/User-Manual/Tiered-Storage_timecho.md

+| **tier** | **data path**                           | **data range**                 | **threshold for minimum remaining disk space** |
+| -------- | -------------------------------------- | ---------------------------- | ------------------------ |
+| tier一   | path 1：/data1/data                    | data for last 1 day              | 20%                      |
+| tier二   | path 1：/data2/data path 2：/data3/data | data from past 1 day to past 10 days | 15%                      |


chrisdutz · 2023-10-17T12:41:00Z

src/UserGuide/V1.2.x/User-Manual/Tiered-Storage_timecho.md

+| -------- | -------------------------------------- | ---------------------------- | ------------------------ |
+| tier一   | path 1：/data1/data                    | data for last 1 day              | 20%                      |
+| tier二   | path 1：/data2/data path 2：/data3/data | data from past 1 day to past 10 days | 15%                      |
+| tier三   | Remote AWS S3 Storage                       | data from 1 day ago         | 10%                      |


wanghui42 and others added 23 commits September 15, 2023 18:58

fix English version

67cc971

fix little wrong

8dfead2

fix more wrong

ca720d0

Merge branch 'apache:main' into new4

68d8e84

add udf of English and fix the rest url

c8fb216

Merge branch 'apache:main' into new4

53bcc10

add url of dbeaver-jar

be2e06d

Update src/UserGuide/Master/Ecosystem-Integration/DBeaver.md

3c2fc92

Co-authored-by: Haonan <hhaonan@outlook.com>

adjust no.6

d7a55e1

Merge branch 'new4' of github.com:wanghui42/iotdb-docs into new4

98c5324

adjust master

bf05d02

Merge branch 'apache:main' into new4

dae5aee

pipe-English

21ee021

1.2-url-English-2

d46019e

3

3759ea5

4

96d7fc9

5

8989685

4

78bd683

5

a3b9ff3

6

c72607d

7

ed18a00

Merge branch 'apache:main' into new4

eb3ffd1

fix title bug and add English doc

478c588

StefanieZhao7 reviewed Oct 17, 2023

View reviewed changes

wanghui42 added 2 commits October 17, 2023 18:38

4

5c1c107

5

f7e39a1

qiaojialin approved these changes Oct 17, 2023

View reviewed changes

qiaojialin merged commit 092d86a into apache:main Oct 17, 2023

chrisdutz requested changes Oct 17, 2023

View reviewed changes


		In this example, two levels of storage are configured, specifically:

		\| 层级 \| 数据目录 \| 数据范围 \| 磁盘最小剩余空间阈值 \|


		In this example, a total of three levels of storage are configured, specifically:

		\| 层级 \| 数据目录 \| 数据范围 \| 磁盘最小剩余空间阈值 \|


		## Benchmark tools

		We also developed Benchmark tools for time series databases

Conversation

wanghui42 commented Oct 11, 2023

Uh oh!

StefanieZhao7 Oct 17, 2023 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

StefanieZhao7 Oct 17, 2023 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

chrisdutz left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

StefanieZhao7 Oct 17, 2023 •

edited

Loading

StefanieZhao7 Oct 17, 2023 •

edited

Loading