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

fix(v3): Apply code review suggestions\ 

Co-authored-by: reidkauffman@users.noreply.github.com
pull/6368/head
Jason Stirnaman 2025-09-09 12:15:29 -05:00 committed by Jason Stirnaman
parent 85b89e353e
commit 2bc9e1736d
1 changed files with 9 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

18
content/shared/v3-distributed-internals-reference/durability.md
View File

@ -20,22 +20,17 @@ When data is written to {{% product-name %}}, it progresses through multiple sta
### Write validation and memory buffer
The [Router](/influxdb3/version/reference/internals/storage-engine/#router) validates incoming data to prevent malformed or unsupported data from entering the system.
{{% product-name %}} writes accepted data to multiple write-ahead-log (WAL) files on local
storage on the [Ingester](/influxdb3/version/reference/internals/storage-engine/#ingester) node before acknowledging the write request.
The Ingester holds the data in memory to ensure leading edge data is available for querying.
{{% product-name %}} writes accepted data to multiple write-ahead log (WAL) files on [Ingester](/influxdb3/version/reference/internals/storage-engine/#ingester) pods' local storage (default is 2 for redundancy) before acknowledging the write request.
The Ingester holds the data in memory to ensure leading-edge data is available for querying.
### Write-ahead log (WAL) persistence
The Ingester persists the contents of
Ingesters persist the contents of
the WAL to Parquet files in object storage and updates the [Catalog](/influxdb3/version/reference/internals/storage-engine/#catalog) to
reference the newly created Parquet files.
{{% hide-in "clustered" %}}
Parquet data files in object storage are redundantly stored on multiple devices
across a minimum of three availability zones in a cloud region.
{{% /hide-in %}}
{{% product-name %}} retains WALs until the data is persisted.
If an Ingester node is gracefully shut down (for example, during a new software deployment), it flushes the contents of the WAL to the Parquet files before shutting down.
{{% product-name %}} retains WALs until the data is persisted to Parquet files in object storage.
## Data storage
@ -45,6 +40,11 @@ point-in-time snapshot of the data. The Parquet files are immutable and are
never replaced nor modified. Parquet files are stored in object storage and
referenced in the [Catalog](/influxdb3/version/reference/internals/storage-engine/#catalog), which InfluxDB uses to find the appropriate Parquet files for a particular set of data.
{{% hide-in "clustered" %}}
Parquet data files in object storage are redundantly stored on multiple devices
across a minimum of three availability zones in a cloud region.
{{% /hide-in %}}
## Data deletion
When data is deleted or expires (reaches the database's [retention period](/influxdb3/version/reference/internals/data-retention/#database-retention-period)), InfluxDB performs the following steps: