Influxdata
/
influxdb
mirror of https://github.com/influxdata/influxdb.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

chore: Apply suggestions from code review 

Co-authored-by: Andrew Lamb <alamb@influxdata.com>
pull/24376/head
Nga Tran 2021-12-20 13:55:07 -05:00 committed by GitHub
parent d2ea7a8eba
commit f2e22bdb1c
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/catalogs.md
View File

@ -9,7 +9,7 @@ Figure 1 below shows the organization of both IOx Catalog and Data. The bottom l
[^cat]: This design might be changed in the future to meet other use cases.
Since the catalog is the central information shared to all users of the database, it needs to keep consistent and integral. Each object of the catalog must be locked in either shared or exclusive mod when accessed or modified. Each catalog object also contains information for us to operate the chunk lifecycle, run queries, as well as measure the health of the system.
Since the catalog is the central information shared to all users of the database, it must be kept consistent. Each object of the catalog must be locked in either shared or exclusive mode when accessed or modified. Each catalog object also contains information to operate the chunk lifecycle, run queries, as well as measure the health of the system.
**Examples of information for operating the chunk lifecycle**
* A chunk includes `LifecycleAction` that keeps track of on-going action of a chunk (e.g. `compacting`, `persisting`) to avoid running the same job on the chunk.