Bound the work-queue durability claim to the appendfsync window

Redis runs with appendfsync everysec, so an unclean stop loses up to a
second of journaled entries. Name that where the docstrings promised a
crash costs nothing, and state the setting and its trade-off on the
configuration page.
This commit is contained in:
2026-09-06 17:16:01 +02:00
parent 6fdc30a4d1
commit e7bf767d40
3 changed files with 13 additions and 2 deletions
+4
View File
@@ -5,6 +5,10 @@ poll — becomes a work item before anything runs. The item is journaled first
and acknowledged only once the wave it started has quiesced, so an engine that
dies mid-cascade picks the work up again on the way back rather than losing it.
Redis journals with ``appendfsync everysec``, so the bound is the last second:
an unclean stop of Redis or of its host loses up to a second of entries. An
engine that dies while Redis lives loses none of them.
Two implementations: Redis Streams, which is what makes the above true, and an
in-memory one for tests and for running without Redis, where "durable" degrades
honestly to "not".