antirez/redis — Issue #163: Back-off when automatic background save fails
Author: pietern
Created: 2011-10-27 00:17:11+00:00
State: open

When Redis should save a snapshot because N changes were made in the last M minutes, this status is only cleared when the background save succeeds. If it is not possible to create the snapshot (e.g. working directory has disappeared, so the file cannot be created), Redis continually retries a background save. A fork is made every time an attempt to create a background save is done, so when it immediately quits because of this error condition, Redis continually forks+retries.

It is an exceptional condition, but maybe we should degrade a little more graceful. Another option is of course to exit altogether when saving is not possible. An argument for this resolution could be that once a user configures saving, Redis shouldn't continue to run when this is no longer possible.

We should discuss this a little bit before continuing; users may depend on the fact that Redis doesn't exit when saving is not (or no longer) possible.