After node changes in the cluster, Vertica continued referencing old node information because stale entries remained in admintools.conf. Although spread.conf was already correctly updated with the new node IPs, the mismatch caused configuration issues. Removing the outdated nodes from admintools.conf and synchronizing the corrected file across the cluster resolved the problem.
Environment
- Product: Vertica Analytics Platform
- Component: admintools.conf, spread.conf
- Tools: Vertica Management Console (MC)
Situation
Vertica showed inconsistent node information after a node replacement or re-IP event.
spread.confcorrectly listed updated node IP addresses.admintools.confstill contained old node entries, causing Vertica utilities to reference stale information.- Management Console (MC) continued showing old node references.
