What steps will reproduce the problem?
1. Set up a redis server with aof disabled
2. Submit a BGREWRITEAOF through redis-cli, for instance
3. appendonly.aof file gets created
What is the expected output? What do you see instead?
I would expect some kind of error message. Still it works as if it was enabled.
What version of the product are you using? On what operating system?
2.2.0-rc2, ubuntu 10.10 linux 32bits
Please provide any additional information below.
I don't want my master redis instance to perform a save to disk if it is
disabled and by mistake it is submitted to it instead of to the persistence
specific slaves.
Original issue reported on code.google.com by jam...@gmail.com on 5 Jan 2011 at 4:15
Original issue reported on code.google.com by
jam...@gmail.com
on 5 Jan 2011 at 4:15