From b7b0c62ff2bfa9fb71ae9ab85716be4702605a79 Mon Sep 17 00:00:00 2001 From: Yoko Hyakuna Date: Tue, 8 Oct 2024 20:49:09 +0000 Subject: [PATCH] backport of commit af8c9571b161c721224e906514650029b1e530fd --- website/content/docs/configuration/replication.mdx | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/website/content/docs/configuration/replication.mdx b/website/content/docs/configuration/replication.mdx index f75d8a0a58b5..a858f9f80efd 100644 --- a/website/content/docs/configuration/replication.mdx +++ b/website/content/docs/configuration/replication.mdx @@ -46,5 +46,11 @@ replication { time to see the resulting WAL present locally before returning a response to the client. - `allow_forwarding_via_token` `(string: "")` - When set to `new_token`, requests sent to non-active nodes are forwarded if the node does not yet have the token information in storage. +- `replication_canary_write_interval_seconds` `(integer: 1)` - Interval in + seconds between writes of the replication canary to the storage on the primary + cluster. Set to 0 to disable the canary. Refer to the [Clock skew and + replication + lag](/vault/docs/enterprise/consistency#clock-skew-and-replication-lag) page + for details on the canary. Support for Server Side Consistent Tokens is now available. Refer to the [Server Side Consistent Token FAQ](/vault/docs/faq/ssct) for details.