mirror of
https://github.com/optim-enterprises-bv/vault.git
synced 2025-11-02 03:27:54 +00:00
backport of commit 4b9b5d60e6 (#23110)
Co-authored-by: soly-hashicorp <106975916+soly-hashicorp@users.noreply.github.com>
This commit is contained in:
committed by
GitHub
parent
cee78a0afd
commit
79cd74d713
@@ -72,7 +72,8 @@ set [`disable_mlock`](/vault/docs/configuration#disable_mlock) to `true`, and to
|
||||
snapshot size and high write throughput causing log truncation before a
|
||||
snapshot can be fully installed. If you need to use this to recover a cluster,
|
||||
consider reducing write throughput or the amount of data stored on Vault. The
|
||||
default value is 10000 which is suitable for all normal workloads.
|
||||
default value is 10000 which is suitable for all normal workloads. The
|
||||
`trailing_logs` metric is not the same as `max_trailing_logs`.
|
||||
|
||||
- `snapshot_threshold` `(integer: 8192)` - This controls the minimum number of Raft
|
||||
commit entries between snapshots that are saved to disk. This is a low-level
|
||||
@@ -84,6 +85,13 @@ set [`disable_mlock`](/vault/docs/configuration#disable_mlock) to `true`, and to
|
||||
snapshot. Servers may take longer to recover from crashes or failover if this
|
||||
is increased significantly as more logs will need to be replayed.
|
||||
|
||||
- `snapshot_interval` `(integer: 120 seconds)` - The snapshot interval
|
||||
controls how often Raft checks whether a snapshot operation is
|
||||
required. Raft randomly staggers snapshots between the configured
|
||||
interval and twice the configured interval to keep the entire cluster
|
||||
from performing a snapshot at once. The default snapshot interval is
|
||||
120 seconds.
|
||||
|
||||
- `retry_join` `(list: [])` - There can be one or more
|
||||
[`retry_join`](#retry_join-stanza) stanzas. When the Raft cluster is getting
|
||||
bootstrapped, if the connection details of all the nodes are known beforehand,
|
||||
|
||||
Reference in New Issue
Block a user