On 24/07/2017 10:43, Daniel Salzman wrote:
Hi Daniel,
> Yes, LMDB itself is designed to be shareable between different threads or
> processes,
> but it has some performance penalty (serialized write operation). Knot DNS
> doesn't
> expect there can be other unknown zones in the timer database.
Hello Anand,
Yes, LMDB itself is designed to be shareable between different threads or
processes,
but it has some performance penalty (serialized write operation). Knot DNS
doesn't
expect there can be other unknown zones in the timer database. Such records are
purged during server reload. But I
Hello Knot developers,
Suppose I am running two Knot DNS instances. They're listening on
different interfaces, and slaving different sets of zones. If the
"storage" variable is the same for these two, then the two instances of
knotd will both try to write into storage/journal and storage/timers.
