Commit 4796a6be authored by Libor Peltan's avatar Libor Peltan Committed by Daniel Salzman

doc: journal behavoiur description improved

parent 928fa6a8
......@@ -856,7 +856,8 @@ DB file size.
.sp
It is recommended to limit \fI\%max\-journal\-usage\fP
per\-zone instead of max\-journal\-size in most cases. Please keep this value
larger than the sum of all zones\(aq journal usage limits.
larger than the sum of all zones\(aq journal usage limits. See more details
regarding journal behaviour\&.
.sp
This value also influences server\(aqs usage of virtual memory.
.sp
......
......@@ -263,8 +263,8 @@ Journal does each operation in one transaction to keep consistency of the DB and
The exception is when store transaction exceeds 5% of the whole DB mapsize, it is split into multiple ones
and some dirty-chunks-management involves.
Each zone journal has own
usage limit on how much DB space it may occupy. Before hitting the limit,
Each zone journal has own :ref:`usage limit <zone_max-journal-usage>`
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 zone file, and oldest changesets are deleted as needed to free
some space. Actually, twice (again, hardcoded constant) the needed amount is deleted to
......@@ -277,6 +277,12 @@ each other, e.g. periodically changing few zone records, re-signing whole zone..
The diff between zone file and zone is thus preserved, even if journal deletes some
older changesets.
There is also a :ref:`safety hard limit <template_max-journal-db-size>` 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. For wiping one zone's journal, see *knotc zone-purge +journal*
command.
.. _Algorithm rollover:
DNSSEC keys algorithm rollover
......
......@@ -993,7 +993,8 @@ DB file size.
It is recommended to limit :ref:`max-journal-usage<zone_max-journal-usage>`
per-zone instead of max-journal-size in most cases. Please keep this value
larger than the sum of all zones' journal usage limits.
larger than the sum of all zones' journal usage limits. See more details
regarding :ref:`journal behaviour<Journal behaviour>`.
This value also influences server's usage of virtual memory.
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment