/sys/storage/raft/autopilot
The /sys/storage/raft/autopilot
endpoints are used to manage raft clusters using autopilot
with Vault's Integrated Storage backend.
Refer to the Integrated Storage Autopilot tutorial to learn how to manage raft clusters using autopilot.
Get Cluster State
This endpoint is used to retrieve the raft cluster state. See the docs page for a description of the output.
Method | Path |
---|---|
GET | /sys/storage/raft/autopilot/state |
Sample Request
Sample Response
Get Configuration
This endpoint is used to get the configuration of the autopilot subsystem of Integrated Storage.
Method | Path |
---|---|
GET | /sys/storage/raft/autopilot/configuration |
Sample Request
Sample Response
Set Configuration
This endpoint is used to modify the configuration of the autopilot subsystem of Integrated Storage.
Method | Path |
---|---|
POST | /sys/storage/raft/autopilot/configuration |
Parameters
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 thatmin-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 whencleanup_dead_servers
is set.max_trailing_logs
(int: 1000)
- Amount of entries in the Raft Log that a server can be behind before being considered unhealthy.min_quorum
(int: 3)
- Minimum number of servers allowed in a cluster before autopilot can prune dead servers. This should at least be 3. Applicable only for voting nodes.server_stabilization_time
(string: "10s")
- Minimum amount of time a server must be in a stable, healthy state before it can be added to the cluster.
Sample Request
Sample Payload