Hi, We have enabled both AOF and RDB. We observed that AOF occupies the entire space allocated causing multiple other issues such as preventing creation of RDB file due to lack of space. Have a couple of questions related to the same.

  1. We have allocated external storage for AOF+RDB file storage. if RAM is 10 GB, how much space should the external storage have? Is 3x (i.e. 30 GB) sufficient space to store AOF files?
  2. If the AOF file occupies 100% of external storage, how to recover from that situation? Can the AOF files be copied to different server to save space here? Will that recreate a new AOF file?

Please advice. Thanks!

Please keep in mind that this issue tracker should be used for reporting bugs or proposing improvements to the Redis server.

Generally, questions about using Redis should be directed to the community:

It is also possible that your question was already asked here, so please do a quick issues search before submitting. Lastly, if your question is about one of Redis' clients, you may to contact your client's developers for help.

That said, please feel free to replace all this with your question :)

Comment From: oranagra

@mukundv18 which redis version are you using? is there anything you can spot in the log files that explains it? can you share your `INFO persistence" output?

  1. this depends on auto-aof-rewrite-percentage, by default it should do a rewrite when the AOF takes twice as much as it did on the last rewrite. IIRC there was a bug in previous redis version, where the size was re-sampled on restart, so that after every restart it'll consider the current size as the base rather than the compact size.
  2. the easy way to recover from that is to disable the appendonly config, delete the file and then re-enable it. it obviously involves some risk.