Apply suggestions from code review

Co-authored-by: Michael Zalimeni <michael.zalimeni@hashicorp.com>
Co-authored-by: Jeff Boruszak <104028618+boruszak@users.noreply.github.com>
zalimeni/dhiaayachi/raft-wal-backend-as-default--suggestions
Dhia Ayachi 2 months ago committed by GitHub
parent 917985e864
commit 5b59260a00
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194

@ -1,4 +1,4 @@
```release-note:enhancement ```release-note:enhancement
use raft-wal as a default raft log store. raft: use raft-wal as the default raft log store.
``` ```

@ -5,7 +5,7 @@ description: >-
Learn how to safely configure and test the experimental WAL backend in your Consul deployment. Learn how to safely configure and test the experimental WAL backend in your Consul deployment.
--- ---
# Enable the experimental WAL LogStore backend # Enable the WAL LogStore backend
WAL LogStore is now enabled by default WAL LogStore is now enabled by default

@ -2,13 +2,13 @@
layout: docs layout: docs
page_title: WAL LogStore Backend Overview page_title: WAL LogStore Backend Overview
description: >- description: >-
The experimental WAL (write-ahead log) LogStore backend shipped in Consul 1.15 is intended to replace the BoltDB backend, improving performance and log storage issues. The write-ahead log (WAL) LogStore is the default backend for Consul. Learn about the WAL backend and how it is different from the BoltDB backend.
--- ---
# WAL LogStore backend overview # Write-ahead Log (WAL) LogStore backend overview
This topic provides an overview of the WAL (write-ahead log) LogStore backend. This topic provides an overview of the WAL (write-ahead log) LogStore backend.
The WAL backend is now the default Consul LogStore when a boltdb database is not already in place. Refer to The WAL backend is now the default Consul LogStore when a BoltDB database is not already in place. Refer to
[Requirements](/consul/docs/agent/wal-logstore/enable#requirements) for [Requirements](/consul/docs/agent/wal-logstore/enable#requirements) for
supported environments and known issues. supported environments and known issues.

@ -7,7 +7,7 @@ description: >-
# Monitor Raft metrics and logs for WAL # Monitor Raft metrics and logs for WAL
This topic describes how to monitor Raft metrics and logs if you are testing the WAL backend. We strongly recommend monitoring the Consul cluster, especially the target server, for evidence that the WAL backend is not functioning correctly. This topic describes how to monitor Raft metrics and logs for the WAL backend. We strongly recommend monitoring the Consul cluster, especially the target server, for evidence that the WAL backend is not functioning correctly.
## Monitor for checksum failures ## Monitor for checksum failures

Loading…
Cancel
Save