5 Kvě
2023
5 Kvě
'23
12:50
On 5/5/23 09:11, libor.peltan wrote:
Anyway, with proper journal configuration, one should prevent any issues
with journal becoming full. It's possible to set per-zone "soft" limits
in a way that the effect of global "hard" limit never takes place.
Hitting the "soft" limit only leads to some internal cleanup, not
affecting DNS service in any way. Read more
https://www.knot-dns.cz/docs/3.2/singlehtml/index.html#journal-behaviour
We have `journal-max-depth` set to 10, everything else set to defaults.
We're not hitting the global hard limit, `journal-db-max-size` is
default 20 GiB and we're nowhere near that.
`journal-max-usage` was at default 100 MiB, raising that to 1 GiB fixed
the problem. We have `zonefile-sync` turned off. According to the docs,
knot will attempt some housekeeping to reduce used space in the journal,
but failing that it should merge changes into the special changeset.
I guess we hit an error when knot tried to merge changesets.
.einar