Re: [knot-dns-users] Best practices for knot inline DNSSEC signing and zone loading

* libor.peltan <libor.peltan(a)nic.cz> [2018-10-29 16:20]: In regards to the journal... well the site states: "There is also a safety hard limit for overall journal database size, but it’s strongly recommended to set the per-zone limits in a way to prevent hitting this one. For LMDB, it’s hard to recover from the database-full state. " "Anyway, it’s recommended to carefully tune the journal-size-related options to avoid surprises of journal getting full." "Each zone journal has own usage limit on how much DB space it may occupy. Before hitting the limit, changesets are stored one-by-one and whole history is linear. While hitting the limit, the zone is flushed into the zone file, and oldest changesets are deleted as needed to free some space." That doesn't sound like the journal can't get full. The only thing that makes me a bit less anxious is this: "If zone file flush is disabled, then instead of flushing the zone, the journal tries to save space by merging older changesets into one. It works well if the changes rewrite each other, e.g. periodically changing few zone records, re-signing whole zone... The difference between the zone file and the zone is thus preserved, even if journal deletes some older changesets." So when I have only DNSSEC stuff in the journal it will not grow because changes are overwritten? Is that what it means? Regards Sebastian -- GPG Key: 0x58A2D94A93A0B9CE (F4F6 B1A3 866B 26E9 450A 9D82 58A2 D94A 93A0 B9CE) 'Are you Death?' ... IT'S THE SCYTHE, ISN'T IT? PEOPLE ALWAYS NOTICE THE SCYTHE. -- Terry Pratchett, The Fifth Elephant