mirror of
https://github.com/kemko/nomad.git
synced 2026-01-01 16:05:42 +03:00
8c57fd5eb0
In #24526 we updated the Consul and Vault fingerprints so that they are no longer periodic. This fixed a problem that cluster admins reported where rolling updates of Vault or Consul would cause a thundering herd of fingerprint updates across the whole cluster. But if Consul/Vault is not available during the initial fingerprint, it will never get fingerprinted again. This is challenging for cluster updates and black starts because the implicit service startup ordering may require reloads. Instead, have the fingerprinter run periodically but mark that it has made its first successful fingerprint of all Consul/Vault clusters. At that point, we can skip further periodic updates. The `Reload` method will reset the mark and allow the subsequent fingerprint to run normally. Fixes: https://github.com/hashicorp/nomad/issues/25097 Ref: https://github.com/hashicorp/nomad/pull/24526 Ref: https://github.com/hashicorp/nomad/issues/24049
4 lines
129 B
Plaintext
4 lines
129 B
Plaintext
```release-note:bug
|
|
fingerprint: Fixed a bug where Consul/Vault would never be fingerprinted if not available on agent start
|
|
```
|