I have redis slaves which are set not to persist any data (save "" and appendonly no).
But after a full resync between these slaves and theirs master the dumps used for this process are being kept.
I think that if redis is set not to persist RDB save "" then these dump should be deleted by redis immediately after loading them.
Without it I have to use ugly workarounds like deleting them with a cron job...
PS It's not only my issue - there's a SO question for that with quite a lot of views: http://stackoverflow.com/questions/9964895/configure-redis-slave-to-stop-saving-data-to-file
Comment From: fidanov
I have the same issue. Especially, because I really need the data to not be persistent, but I am afraid that if the server crashes this dump file might loaded.
Thankfully, no crashes so far and I am removing the dump files manually, but this should be automated.
Comment From: obriat
This specially painful if you use a master/slave with no persistency (typically a cache backend). If a Slave became a master and is restarted, it loads the last sync dump file !
See also #1704 #2167
Comment From: 029vaibhav
so can we assume that master-slave configuration with persistence off is still persisting because BGSAVE save is used to sync between them.??
Comment From: antirez
Looking into this.
Comment From: antirez
Please check the "nordb" branch that implements this. Yet not merged into "unstable".
Comment From: kkmuffme
Hope this gets merged soon, as this really is unintuitive and adds additional stress (to the admin staff) in failover cases, where a former slave needs to be restarted and nobody knows about this "feature".
If a Slave became a master and is restarted, it loads the last sync dump file !