Redis数据持久化之AOF模式

1、AOF是什么？

• AOF(Append Only File):是指以日志的形式来记录每个写操作，将Redis执行过的所有写指令记录下来(读操作不记录)， 默认保存为appendonly.aof文件 , 只许追加文件但不可以改写文件，Redis启动之初会读取该文件重新构建数据。

2、AOF配置文件详解

############################## APPEND ONLY MODE(追加) ###############################

# By default Redis asynchronously dumps the dataset on disk. This mode is
# good enough in many applications, but an issue with the Redis process or
# a power outage may result into a few minutes of writes lost (depending on
# the configured save points).
# 默认情况下，redis异步地将数据集转储到磁盘上。此模式是在许多应用程序中已经足够好了，但Redis进程有问题，或者断电可能导致几分钟的写入丢失（取决于配置的保存点）。
#
# The Append Only File is an alternative persistence mode that provides
# much better durability. For instance using the default data fsync policy
# (see later in the config file) Redis can lose just one second of writes in a
# dramatic event like a server power outage, or a single write if something
# wrong with the Redis process itself happens, but the operating system is
# still running correctly.
#
# AOF and RDB persistence can be enabled at the same time without problems.
# If the AOF is enabled on startup Redis will load the AOF, that is the file
# with the better durability guarantees.
# AOF和RDB持久性可以同时启用，不会出现问题。
# 如果在启动时启用了AOF，redis将加载AOF，即文件具有更好的耐久性保证。
#
# Please check http://redis.io/topics/persistence for more information.
#
# 默认关闭,设置为yes即可开机aof
#
appendonly no

# The name of the append only file (default: "appendonly.aof")
# 指定更新日志文件名，默认为appendonly.aof
#
appendfilename "appendonly.aof"

# The fsync() call tells the Operating System to actually write data on disk
# instead of waiting for more data in the output buffer. Some OS will really flush
# data on disk, some other OS will just try to do it ASAP.
#
# Redis supports three different modes:
#
# no: don't fsync, just let the OS flush the data when it wants. Faster.
# always: fsync after every write to the append only log. Slow, Safest.
# everysec: fsync only one time every second. Compromise.
#
# The default is "everysec", as that's usually the right compromise between
# speed and data safety. It's up to you to understand if you can relax this to
# "no" that will let the operating system flush the output buffer when
# it wants, for better performances (but if you can live with the idea of
# some data loss consider the default persistence mode that's snapshotting),
# or on the contrary, use "always" that's very slow but a bit safer than
# everysec.
#
# More details please check the following article:
# http://antirez.com/post/redis-persistence-demystified.html
#
# If unsure, use "everysec".
# If unsure, use "everysec".
#
# appendfsync always
# 同步持久化 每次发生数据变更会被立即记录到磁盘  性能较差但数据完整性比较高

# 表示每秒同步一次（折衷，默认值）
appendfsync everysec

# appendfsync no
# 从不同步

# When the AOF fsync policy is set to always or everysec, and a background
# saving process (a background save or AOF log background rewriting) is
# performing a lot of I/O against the disk, in some Linux configurations
# Redis may block too long on the fsync() call. Note that there is no fix for
# this currently, as even performing fsync in a different thread will block
# our synchronous write(2) call.
#
# In order to mitigate this problem it's possible to use the following option
# that will prevent fsync() from being called in the main process while a
# BGSAVE or BGREWRITEAOF is in progress.
#
# This means that while another child is saving, the durability of Redis is
# the same as "appendfsync none". In practical terms, this means that it is
# possible to lose up to 30 seconds of log in the worst scenario (with the
# default Linux settings).
#
# If you have latency problems turn this to "yes". Otherwise leave it as
# "no" that is the safest pick from the point of view of durability.
#
# 重写时是否可以运用Appendfsync，用默认no即可，保证数据安全性。
#
no-appendfsync-on-rewrite no

# Automatic rewrite of the append only file.
# Redis is able to automatically rewrite the log file implicitly calling
# BGREWRITEAOF when the AOF log size grows by the specified percentage.
#
# This is how it works: Redis remembers the size of the AOF file after the
# latest rewrite (if no rewrite has happened since the restart, the size of
# the AOF at startup is used).
#
# This base size is compared to the current size. If the current size is
# bigger than the specified percentage, the rewrite is triggered. Also
# you need to specify a minimal size for the AOF file to be rewritten, this
# is useful to avoid rewriting the AOF file even if the percentage increase
# is reached but it is still pretty small.
#
# Specify a percentage of zero in order to disable the automatic AOF
# rewrite feature.
#
# 当aof文件过大时,设置重写的基准值
#
auto-aof-rewrite-percentage 100
auto-aof-rewrite-min-size 64mb

# An AOF file may be found to be truncated at the end during the Redis
# startup process, when the AOF data gets loaded back into memory.
# This may happen when the system where Redis is running
# crashes, especially when an ext4 filesystem is mounted without the
# data=ordered option (however this can't happen when Redis itself
# crashes or aborts but the operating system still works correctly).
#
# Redis can either exit with an error when this happens, or load as much
# data as possible (the default now) and start if the AOF file is found
# to be truncated at the end. The following option controls this behavior.
#
# If aof-load-truncated is set to yes, a truncated AOF file is loaded and
# the Redis server starts emitting a log to inform the user of the event.
# Otherwise if the option is set to no, the server aborts with an error
# and refuses to start. When the option is set to no, the user requires
# to fix the AOF file using the "redis-check-aof" utility before to restart
# the server.
#
# Note that if the AOF file will be found to be corrupted in the middle
# the server will still exit with an error. This option only applies when
# Redis will try to read more data from the AOF file but not enough bytes
# will be found.
#
aof-load-truncated yes

3、AOF数据恢复

• 正常恢复
  ① 修改默认的appendonly no，改为yes
  ② 拷贝备份好的appendonly.aof至服务启动目录,可通过config get dir获取
  ③ 重新启动redis服务即可

• 异常恢复
  ① 修改默认的appendonly no，改为yes
  ② 备份appendonly.aof文件，通过执行redis-check-aof --fix appendonly.aof命令进行修复。
  ③ 重新启动redis服务

4、AOF的重写策略(ReWrite)

1):简述

• AOF采用文件追加方式，文件会越来越大为避免出现此种情况，新增了重写机制,当AOF文件的大小超过所设定的阈值时，Redis就会启动AOF文件的内容压缩，只保留可以恢复数据的最小指令集.可以使用命令bgrewriteaof。

2):重写原理

• AOF文件持续增长而过大时，会fork出一条新进程来将文件重写(也是先写临时文件最后再rename)，遍历新进程的内存中数据，每条记录有一条的Set语句。重写aof文件的操作，并没有读取旧的aof文件，而是将整个内存中的数据库内容用命令的方式重写了一个新的aof文件。

3):触发机制

• Redis会记录上次重写时的AOF大小，默认配置是当AOF文件大小是上次rewrite后大小的一倍且文件大于64M时触发

5、AOF的优缺点

• 优点
  ① appendfsync always ：同步持久化 每次发生数据变更会被立即记录到磁盘 性能较差但数据完整性比较好。
  ② appendfsync everysec : 异步操作，每秒记录 如果一秒内宕机，有数据丢失。
  ③ appendfsync no : 从不同步。

• 缺点
  ① 相同数据集的数据而言aof文件要远大于rdb文件，恢复速度慢于rdb。
  ② Aof运行效率要慢于rdb,每秒同步策略效率较好，不同步效率和rdb相同。