5 Kvě
2023
5 Kvě
'23
11:24
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
On 5/5/23 09:16, Anand Buddhdev wrote:
On 05/05/2023 11:01, Einar Bjarni Halldórsson wrote:
kjournalprint -dz will report journal usage, both per zone and total.
The Knot DNS journal provides many advantages over plain files, but this
is one of its major downsides, and needs careful monitoring. We have run
into this at RIPE NCC as well. Older versions of Knot DNS didn't manage
journal usage well, and it led to lots of fragmentation.
I don't know which version of Knot you're running, but newer versions
have improvements in the journal code to avoid some of those problems.
If possible, you should upgrade to the latest version.
Thank you very much Libor and Anand!
This was exactly the information I was looking for.
We're running 3.2.6 and this is the first problem we've hit since going
into production more than a year ago. One gotcha for more than a year of
zero issue running is pretty good :)
.einar