This article explains the expected behavior observed in Vertica logs related to transient network changes, missed heartbeats, and node eviction. Configuration changes were applied to increase tolerance for network latency and reduce false positives.
Environment
- Vertica Cluster
- Spread communication layer
- Vertica version with default heartbeat and token timeout settings
Situation
A Vertica node was evicted from the cluster following a series of log entries indicating:
-
Spread Network Change Messages
NETWORK change with 1 VS setsThese entries indicate transient network or membership changes, where Spread re-established a single stable view of the cluster.
