42296292a4
This fixes pathological cases where the write throughput and snapshot size are both so large that more than 10k log entries are written in the time it takes to restore the snapshot from disk. In this case followers that restart can never catch up with leader replication again and enter a loop of constantly downloading a full snapshot and restoring it only to find that snapshot is already out of date and the leader has truncated its logs so a new snapshot is sent etc. In general if you need to adjust this, you are probably abusing Consul for purposes outside its design envelope and should reconsider your usage to reduce data size and/or write volume. |
||
|---|---|---|
| .. | ||
| basics.html.md | ||
| checks.html.md | ||
| cloud-auto-join.html.md | ||
| config_entries.html.md | ||
| dns.html.md | ||
| encryption.html.md | ||
| kv.html.md | ||
| options.html.md | ||
| rpc.html.md | ||
| sentinel.html.markdown.erb | ||
| services.html.md | ||
| telemetry.html.md | ||
| watches.html.md | ||