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

fix: update compact-throughput default values, closes influxdata/DAR#568 (#6573)

pull/6576/head^2
Scott Anderson 2025-11-25 18:14:17 -07:00 committed by GitHub
parent 0fcf2bdd31
commit 20a736303e
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
2 changed files with 10 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
content/enterprise_influxdb/v1/administration/configure/config-data-nodes.md
View File

@ -425,7 +425,7 @@ Environmental variable: `INFLUXDB_DATA_CACHE_MAX_CONCURRENT_COMPACTIONS`
#### compact-throughput
Default is `50331648`.
Default is `"48m"`.
The maximum number of bytes per seconds TSM compactions write to disk. Default is `"48m"` (48 million).
Note that short bursts are allowed to happen at a possibly larger value, set by `compact-throughput-burst`.
@ -435,7 +435,7 @@ Environment variable: `INFLUXDB_DATA_COMPACT_THROUGHPUT`
#### compact-throughput-burst
Default is `50331648`.
Default is `"48m"`.
The maximum number of bytes per seconds TSM compactions write to disk during brief bursts. Default is `"48m"` (48 million).
@ -453,9 +453,9 @@ Environment variable: `INFLUXDB_DATA_COMPACT_FULL_WRITE_COLD_DURATION`
Default is `10000`.
The number of points per block to use during aggressive compaction. There are
certain cases where TSM files do not get fully compacted. This adjusts an
internal parameter to help ensure these files do get fully compacted.
The number of points per block to use during aggressive compaction. In certain
cases, TSM files do not get fully compacted. This adjusts an internal parameter
to help ensure these files do get fully compacted.
Environment variable: `INFLUXDB_DATA_AGGRESSIVE_POINTS_PER_BLOCK`
@ -841,7 +841,7 @@ Environment variable: `INFLUXDB_HINTED_HANDOFF_RETRY_RATE_LIMIT`
Default is `"1s"`.
The time period after which the hinted handoff retries a write after the write fails. There is an exponential back-off, which starts at 1 second and increases with each failure until it reaches `retry-max-interval`. Retries will then occur at the `retry-max-interval`. Once there is a successful retry, the waiting period will be reset to the `retry-interval`.
The time period after which the hinted handoff retries a write after the write fails. An exponential back-off starts at 1 second and increases with each failure until it reaches `retry-max-interval`. Retries then occur at the `retry-max-interval`. Once there is a successful retry, the waiting period is reset to the `retry-interval`.
Environment variable: `INFLUXDB_HINTED_HANDOFF_RETRY_INTERVAL`

8
content/influxdb/v1/administration/config.md
View File

@ -115,7 +115,7 @@ Uncommented settings override the internal defaults.
Note that the local configuration file does not need to include every
configuration setting.
There are two ways to launch InfluxDB with your configuration file:
Use one of the following methods to start InfluxDB with your configuration file:
- Point the process to the configuration file by using the `-config`
option. For example:
@ -430,9 +430,9 @@ brief bursts.
#### aggressive-points-per-block {metadata="v1.12.0+"}
The number of points per block to use during aggressive compaction. There are
certain cases where TSM files do not get fully compacted. This adjusts an
internal parameter to help ensure these files do get fully compacted.
The number of points per block to use during aggressive compaction. In certain
cases, TSM files do not get fully compacted. This adjusts an internal parameter
to help ensure these files do get fully compacted.
**Default**: `10000`
**Environment variable**: `INFLUXDB_AGGRESSIVE_POINTS_PER_BLOCK`