Introduction
In a Vault Enterprise cluster with performance_standby
enabled, a Performance Standby node is restarted within the same High Availability (HA) cluster. This behavior may lead to observations about the Performance Standby Last Remote WAL metric immediately after the restart.
Problem:
After restarting the Vault service on a Performance Standby node, the Performance Standby Last Remote WAL metric may initially display a value of 0
.
Prerequisites (if applicable):
This behavior is specific to Vault Enterprise because the Performance Standby feature is part of the Enterprise Premium offering.
Cause:
This behavior is expected and works as designed. The Performance Standby Last Remote WAL metric remains at 0
until a write operation occurs on the leader node, which then triggers WAL updates.
References:
-
HashiCorp Documentation on Replication Concepts:
https://developer.hashicorp.com/vault/docs/enterprise/replication/concepts -
Performance Replication Overview:
https://developer.hashicorp.com/vault/docs/enterprise/replication/performance -
Enable Performance Replication:
https://developer.hashicorp.com/vault/docs/enterprise/replication/enable-performance-replication