Add 'note' for surpassing dead server threshold time (#17455)
* Add 'note' for surpassing dead server threshold time * Update website/content/docs/commands/operator/raft.mdx Co-authored-by: Nick Cabatoff <ncabatoff@hashicorp.com> Co-authored-by: Nick Cabatoff <ncabatoff@hashicorp.com>
This commit is contained in:
parent
412603befd
commit
191f6e4bf0
|
@ -325,8 +325,10 @@ Flags applicable to this command are the following:
|
|||
go without leader contact before being considered unhealthy. Defaults to `10s`.
|
||||
|
||||
- `dead-server-last-contact-threshold` `(string)` - 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. Defaults to `24h`.
|
||||
a server can go without leader contact before being considered failed.
|
||||
This takes effect only when `cleanup_dead_servers` is set as `true`. Defaults to `24h`.
|
||||
|
||||
-> **Note:** A failed server that autopilot has removed from the raft configuration cannot rejoin the cluster without being reinitialized.
|
||||
|
||||
- `max-trailing-logs` `(int)` - Amount of entries in the Raft Log that a server
|
||||
can be behind before being considered unhealthy. Defaults to `1000`.
|
||||
|
|
Loading…
Reference in New Issue