upstream/vault
1
0
Fork 0
mirror of https://github.com/hashicorp/vault.git synced 2026-06-11 09:51:16 -04:00
Code Issues Projects Releases Packages Wiki Activity Actions 9

Docs/autopilot typo fix and DR autopilot clarification (#12596)

Browse source 
* autopilot cleanup and parameter typo cleanup

* clarify DR AP lives now

* typo myself cleanup

* trigger ci

Co-authored-by: aphorise <aphorise@gmail.com>
Co-authored-by: taoism4504 <loann@hashicorp.com>
This commit is contained in:
Mike Green 2022-08-19 15:30:13 -06:00 committed by GitHub
parent d5478974f7
commit 98bfa650b1
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
2 changed files with 5 additions and 8 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

5
website/content/api-docs/system/storage/raftautopilot.mdx
View file

@ -5,7 +5,6 @@ description: |-
The `/sys/storage/raft/autopilot` endpoints are used to manage raft clusters using autopilot with Vault's Integrated Storage backend.
These endpoints are inactive on DR secondaries currently.
---
# `/sys/storage/raft/autopilot`
@ -204,14 +203,14 @@ This endpoint is used to modify the configuration of the autopilot subsystem of
- `cleanup_dead_servers` `(bool: false)` - Controls whether to remove dead servers from
the Raft peer list periodically or when a new server joins. This requires that
`min-quorum` is also set.
`min_quorum` is also set.
- `last_contact_threshold` `(string: "10s")` - Limit on the amount of time a server can
go without leader contact before being considered unhealthy.
- `dead_server_last_contact_threshold` `(string: "24h")` - Limit on the amount of time
a server can go without leader contact before being considered failed. This
takes effect only when `cleanup_dead_servers` is set.
takes effect only when `cleanup_dead_servers` is `true`.
- `max_trailing_logs` `(int: 1000)` - Amount of entries in the Raft Log that a server
can be behind before being considered unhealthy.

8
website/content/docs/concepts/integrated-storage/autopilot.mdx
View file

@ -97,13 +97,11 @@ increase read scalability.
## Replication
Performance secondary clusters have their own Autopilot configuration, managed
DR secondary and Performance secondary clusters have their own Autopilot configurations, managed
independently of their primary.
DR secondary clusters will also have their own Autopilot configuration (starting
in Vault 1.8.0), managed independently of their primary. The [Autopilot
API](/api-docs/system/storage/raftautopilot) uses DR operation tokens for
authorization.
The [Autopilot API](/api/system/storage/raftautopilot) uses DR operation tokens for
authorization when executed against a DR secondary cluster.
## Tutorial