[opendmarc-dev] Delayed DB writes
Andreas Schulze
sca at andreasschulze.de
Wed Jun 20 11:48:16 PDT 2012
> 2) Write things to a flat text file which then gets batch-imported when
> the database is available (maybe by cron, maybe by a separate filter
> thread); if the flat file can't be written (disk full or such), fall back
> to 1
-1: too much external dependencies
> 3) Queue some number of events internally and then replay the queue into
> the DB when it's available; when the queue gets too large, fall back to 1
sounds reasonable and would be tolerant agains short db outages.
If implemented as fifo of fixed (configurable) length batch writes would be possible too.
If limits (fifo usage) are reached a descriptive logging should help the admin
to adjust the fifo size to local needs.
Andreas
More information about the opendmarc-dev
mailing list