mara/hyperhive
mara/hyperhive
Watch
0
0
Fork
You've already forked hyperhive
 0
Code Activity

metrics auth responders keep the last good bearer while the store doesn't answer

Browse source
This commit is contained in:
atlas 2026-11-04 17:21:28 +01:00
commit dff2f3ca4d
1 changed files with 325 additions and 145 deletions
Download patch file Download diff file Expand all files Collapse all files

11
docs/swarm/services.md
View file

@ -266,8 +266,15 @@ Where the secret store runs on the same host, these default to the leaf it
mints. On any other host you place a leaf whose CN is
`deploy.bao.metricsAuthCommonName`, and evaluation refuses the config until
you set both. `swarm-metrics-auth` reads the stored bearer at most once a
minute, so a replaced bearer starts working up to a minute later. After a
failed or timed-out read it denies for three seconds without trying again.
minute, so a replaced bearer starts working up to a minute later. When the
store doesn't answer within five seconds, it checks requests against the
last value it read instead of denying, and still refuses a wrong bearer;
it tries the store again after three seconds. A revoked or rotated bearer
stays accepted for as long as the store is down. The store's next answer
replaces the value, and a process that has read none yet (it started while
the store was down) denies. `swarm-logs-grafana-auth`
is the same binary and does the same.
`swarm-metrics-agent-auth` is the log store's `swarm-logs-auth` binary, with
the same grant TTL and rate limit, under `deploy.victoriametrics.agentAuth*`
(table above).