Linux redis 配置文件
# Redis configuration file example
# Note on units: when memory size is needed, it is possible to specify
# it in the usual form of 1k 5GB 4M and so forth:
# 內存大小的配置，下面是內存大小配置的轉換方式
#
# 1k => 1000 bytes
# 1kb => 1024 bytes
# 1m => 1000000 bytes
# 1mb => 1024*1024 bytes
# 1g => 1000000000 bytes
# 1gb => 1024*1024*1024 bytes
#
# units are case insensitive so 1GB 1Gb 1gB are all the same.
# 內存大小的配置，不區分大小寫
################################## INCLUDES ###################################
# Include one or more other config files here. This is useful if you
# have a standard template that goes to all Redis server but also need
# to customize a few per-server settings. Include files can include
# other files, so use this wisely.
#
# Notice option "include" won't be rewritten by command "CONFIG REWRITE"
# from admin or Redis Sentinel. Since Redis always uses the last processed
# line as value of a configuration directive, you'd better put includes
# at the beginning of this file to avoid overwriting config change at runtime.
#
# If instead you are interested in using includes to override configuration
# options, it is better to use include as the last line.
#
# include /path/to/local.conf
# include /path/to/other.conf
# 當配置多個redis時，可能大部分配置一樣，而對於不同的redis，只有少部分配置需要定製
# 就可以配置一個公共的模板配置。
# 對於具體的reids，只需設置少量的配置，並用include把模板配置包含進來即可。
#
# 值得注意的是，對於同一個配置項，redis只對最後一行的有效
# 所以爲避免模板配置覆蓋當前配置，應在配置文件第一行使用include
# 當然，如果模板配置的優先級比較高，就在配置文件最後一行使用include
################################ GENERAL #####################################
# By default Redis does not run as a daemon. Use 'yes' if you need it.
# Note that Redis will write a pid file in /var/run/redis.pid when daemonized.
# yes爲使用守護進程，此時redis的進程ID會被寫進 pidfile的配置中
daemonize yes
# When running daemonized, Redis writes a pid file in /var/run/redis.pid by
# default. You can specify a custom pid file location here.
# 當redis以守護進程的方式啓動時，redis的進程ID將會寫在這個文件中
pidfile /var/run/redis.pid
# Accept connections on the specified port, default is 6379.
# If port 0 is specified Redis will not listen on a TCP socket.
# redis 啓動的端口。【應該知道redis是服務端吧】
port 6379
# TCP listen() backlog.
#
# In high requests-per-second environments you need an high backlog in order
# to avoid slow clients connections issues. Note that the Linux kernel
# will silently truncate it to the value of /proc/sys/net/core/somaxconn so
# make sure to raise both the value of somaxconn and tcp_max_syn_backlog
# in order to get the desired effect.
# 最大鏈接緩衝池的大小，這裏應該是指的未完成鏈接請求的數量
#（測試值爲1時，仍可以有多個鏈接）
# 但該值與listen函數中的backlog意義應該是相同的，源碼中該值就是被用在了listen函數中
# 該值同時受/proc/sys/net/core/somaxconn 和 tcp_max_syn_backlog（/etc/sysctl.conf中配置）的限制
# tcp_max_syn_backlog 指的是未完成鏈接的數量
tcp-backlog 511
# By default Redis listens for connections from all the network interfaces
# available on the server. It is possible to listen to just one or multiple
# interfaces using the "bind" configuration directive, followed by one or
# more IP addresses.
# 綁定ip，指定ip可以連接到redis
#
# Examples:
#
# bind 192.168.1.100 10.0.0.1
# bind 127.0.0.1
# Specify the path for the Unix socket that will be used to listen for
# incoming connections. There is no default, so Redis will not listen
# on a unix socket when not specified.
#
# 這個應該就是以文件形式創建的socket
# unixsocket /tmp/redis.sock
# unixsocketperm 755
# Close the connection after a client is idle for N seconds (0 to disable)
# 超時斷鏈機制，如果一個鏈接在N秒內沒有任何操作，則斷開該鏈接
# N爲0時，該機制失效
timeout 0
# TCP keepalive.
#
# If non-zero, use SO_KEEPALIVE to send TCP ACKs to clients in absence
# of communication. This is useful for two reasons:
#
# 1) Detect dead peers.
# 2) Take the connection alive from the point of view of network
# equipment in the middle.
#
# On Linux, the specified value (in seconds) is the period used to send ACKs.
# Note that to close the connection the double of the time is needed.
# On other kernels the period depends on the kernel configuration.
# 就像心跳檢測一樣，檢查鏈接是否保持正常，同時也可以保持正常鏈接的通信
# 建議值爲60
#
# A reasonable value for this option is 60 seconds.
tcp-keepalive 0
# Specify the server verbosity level.
# This can be one of:
# debug (a lot of information, useful for development/testing)
# verbose (many rarely useful info, but not a mess like the debug level)
# notice (moderately verbose, what you want in production probably)
# warning (only very important / critical messages are logged)
# 日誌級別
loglevel notice
# Specify the log file name. Also the empty string can be used to force
# Redis to log on the standard output. Note that if you use standard
# output for logging but daemonize, logs will be sent to /dev/null
# 日誌存放路徑，默認是輸出到標準輸出，但當以守護進程方式啓動時，默認輸出到/dev/null(傳說中的linux黑洞)
logfile ""
# To enable logging to the system logger, just set 'syslog-enabled' to yes,
# and optionally update the other syslog parameters to suit your needs.
# yes 表示將日誌寫到系統日誌中
# syslog-enabled no
# Specify the syslog identity.
# 當syslog-enabled爲yes時，指定系統日誌的標示爲 redis
# syslog-ident redis
# Specify the syslog facility. Must be USER or between LOCAL0-LOCAL7.
# 指定系統日誌的設備
# syslog-facility local0
# Set the number of databases. The default database is DB 0, you can select
# a different one on a per-connection basis using SELECT <dbid> where
# dbid is a number between 0 and 'databases'-1
# redis的數據庫格式，默認16個(0~15)，默認使用第0個。
databases 16
################################ SNAPSHOTTING ################################
#
# Save the DB on disk:
#
# save <seconds> <changes>
#
# Will save the DB if both the given number of seconds and the given
# number of write operations against the DB occurred.
# 快照，即將數據寫到硬盤上，在<seconds>秒內，至少有<changes>次寫入數據庫操作
# 則會將數據寫入硬盤一次。
# 將save行註釋掉則永遠不會寫入硬盤
# save "" 表示刪除所有的快照點
#
# In the example below the behaviour will be to save:
# after 900 sec (15 min) if at least 1 key changed
# after 300 sec (5 min) if at least 10 keys changed
# after 60 sec if at least 10000 keys changed
#
# Note: you can disable saving at all commenting all the "save" lines.
#
# It is also possible to remove all the previously configured save
# points by adding a save directive with a single empty string argument
# like in the following example:
#
# save ""
save 900 1
save 300 10
save 60 10000
# By default Redis will stop accepting writes if RDB snapshots are enabled
# (at least one save point) and the latest background save failed.
# This will make the user aware (in a hard way) that data is not persisting
# on disk properly, otherwise chances are that no one will notice and some
# disaster will happen.
#
# If the background saving process will start working again Redis will
# automatically allow writes again.
#
# However if you have setup your proper monitoring of the Redis server
# and persistence, you may want to disable this feature so that Redis will
# continue to work as usual even if there are problems with disk,
# permissions, and so forth.
# 當做快照失敗的時候，redis會停止繼續向其寫入數據，保證第一時間發現redis快照出現問題
# 當然，通過下面配置爲 no，即使redis快照失敗，也能繼續向redis寫入數據
stop-writes-on-bgsave-error yes
# Compress string objects using LZF when dump .rdb databases?
# For default that's set to 'yes' as it's almost always a win.
# If you want to save some CPU in the saving child set it to 'no' but
# the dataset will likely be bigger if you have compressible values or keys.
# 快照的時候，是否用LZF壓縮，使用壓縮會佔一定的cpu，但不使用壓縮，快照會很大
rdbcompression yes
# Since version 5 of RDB a CRC64 checksum is placed at the end of the file.
# This makes the format more resistant to corruption but there is a performance
# hit to pay (around 10%) when saving and loading RDB files, so you can disable it
# for maximum performances.
#
# RDB files created with checksum disabled have a checksum of zero that will
# tell the loading code to skip the check.
# 數據校驗，快照末尾會存放一個校驗值，保證數據的準確性
# 但數據校驗會使性能下降約10%，默認開啓校驗
rdbchecksum yes
# The filename where to dump the DB
# 快照的名字
dbfilename dump.rdb
# The working directory.
#
# The DB will be written inside this directory, with the filename specified
# above using the 'dbfilename' configuration directive.
#
# The Append Only File will also be created inside this directory.
#
# Note that you must specify a directory here, not a file name.
#
# 快照存放的目錄
# linux root下測試，會發現該進程會在當前目錄下創建一個dump.rdb
# 但快照卻放在了根目錄/下，重啓的時候，是不會從快照中恢復數據的
# 當把根目錄下的dump.rdb文件拷貝到當前目錄的時候，再次啓動，就會從快照中恢復數據
# 而且以後的快照也都在當前目錄的dump.rdb中做操作
#
# 值得一提的是，快照是異步方式的，如果在還未達到快照的時候，修改了數據，而且redis發生問題crash了
# 那麼中間的修改數據是不會被保存到dump.rdb快照中的
# 解決辦法就是用Append Only Mode的同步模式(下面將會有該配置項)
# 將會把每個操作寫到Append Only File中，該文件也存放於當前配置的目錄
# 建議使用絕對路徑！！！
#
dir ./
################################# REPLICATION #################################
# Master-Slave replication. Use slaveof to make a Redis instance a copy of
# another Redis server. Note that the configuration is local to the slave
# so for example it is possible to configure the slave to save the DB with a
# different interval, or to listen to another port, and so on.
#
# 主從複製，類似於雙機備份。
# 配置需指定主機的ip 和port
# slaveof <masterip> <masterport>
# If the master is password protected (using the "requirepass" configuration
# directive below) it is possible to tell the slave to authenticate before
# starting the replication synchronization process, otherwise the master will
# refuse the slave request.
#
# 如果主機redis需要密碼，則指定密碼
# 密碼配置在下面安全配置中
# masterauth <master-password>
# When a slave loses its connection with the master, or when the replication
# is still in progress, the slave can act in two different ways:
#
# 1) if slave-serve-stale-data is set to 'yes' (the default) the slave will
# still reply to client requests, possibly with out of date data, or the
# data set may just be empty if this is the first synchronization.
#
# 2) if slave-serve-stale-data is set to 'no' the slave will reply with
# an error "SYNC with master in progress" to all the kind of commands
# but to INFO and SLAVEOF.
#
# 當從機與主機斷開時，即同步出現問題的時候，從機有兩種處理方式
# yes, 繼續響應客戶端請求，但可能有髒數據（過期數據、空數據等）
# no，對客戶端的請求統一回復爲“SYNC with master in progress”，除了INFO和SLAVEOF命令
slave-serve-stale-data yes
# You can configure a slave instance to accept writes or not. Writing against
# a slave instance may be useful to store some ephemeral data (because data
# written on a slave will be easily deleted after resync with the master) but
# may also cause problems if clients are writing to it because of a
# misconfiguration.
#
# Since Redis 2.6 by default slaves are read-only.
#
# Note: read only slaves are not designed to be exposed to untrusted clients
# on the internet. It's just a protection layer against misuse of the instance.
# Still a read only slave exports by default all the administrative commands
# such as CONFIG, DEBUG, and so forth. To a limited extent you can improve
# security of read only slaves using 'rename-command' to shadow all the
# administrative / dangerous commands.
# slave只讀選項，設置從機只讀（默認）。
# 即使設置可寫，當下一次從主機上同步數據，仍然會刪除當前從機上寫入的數據
# 【待測試】：主機與從機互爲slave會出現什麼情況？
# 【預期三種結果】：1. 提示報錯 2. 主從服務器數據不可控 3. 一切正常
slave-read-only yes
# Slaves send PINGs to server in a predefined interval. It's possible to change
# this interval with the repl_ping_slave_period option. The default value is 10
# seconds.
#
# 從服務器向主服務器發送心跳包，默認10發送一次
# repl-ping-slave-period 10
# The following option sets the replication timeout for:
#
# 1) Bulk transfer I/O during SYNC, from the point of view of slave.
# 2) Master timeout from the point of view of slaves (data, pings).
# 3) Slave timeout from the point of view of masters (REPLCONF ACK pings).
#
# It is important to make sure that this value is greater than the value
# specified for repl-ping-slave-period otherwise a timeout will be detected
# every time there is low traffic between the master and the slave.
#
# 超時響應時間，值必須比repl-ping-slave-period大
# 批量數據傳輸超時、ping超時
# repl-timeout 60
# Disable TCP_NODELAY on the slave socket after SYNC?
#
# If you select "yes" Redis will use a smaller number of TCP packets and
# less bandwidth to send data to slaves. But this can add a delay for
# the data to appear on the slave side, up to 40 milliseconds with
# Linux kernels using a default configuration.
#
# If you select "no" the delay for data to appear on the slave side will
# be reduced but more bandwidth will be used for replication.
#
# By default we optimize for low latency, but in very high traffic conditions
# or when the master and slaves are many hops away, turning this to "yes" may
# be a good idea.
# 主從同步是否延遲
# yes 有延遲，約40毫秒（linux kernel的默認配置），使用較少的數據包，較小的帶寬
# no 無延遲（減少延遲），但需要更大的帶寬
repl-disable-tcp-nodelay no
# Set the replication backlog size. The backlog is a buffer that accumulates
# slave data when slaves are disconnected for some time, so that when a slave
# wants to reconnect again, often a full resync is not needed, but a partial
# resync is enough, just passing the portion of data the slave missed while
# disconnected.
#
# The biggest the replication backlog, the longer the time the slave can be
# disconnected and later be able to perform a partial resynchronization.
#
# The backlog is only allocated once there is at least a slave connected.
#
# 默認情況下，當slave重連的時候，會進行全量數據同步
# 但實際上slave只需要部分同步即可，這個選項設置部分同步的大小
# 設置值越大，同步的時間就越長
# repl-backlog-size 1mb
# After a master has no longer connected slaves for some time, the backlog
# will be freed. The following option configures the amount of seconds that
# need to elapse, starting from the time the last slave disconnected, for
# the backlog buffer to be freed.
#
# A value of 0 means to never release the backlog.
#
# 主機的後臺日誌釋放時間，即當沒有slave連接時，過多久釋放後臺日誌
# 0表示不釋放
# repl-backlog-ttl 3600
# The slave priority is an integer number published by Redis in the INFO output.
# It is used by Redis Sentinel in order to select a slave to promote into a
# master if the master is no longer working correctly.
#
# A slave with a low priority number is considered better for promotion, so
# for instance if there are three slaves with priority 10, 100, 25 Sentinel will
# pick the one with priority 10, that is the lowest.
#
# However a special priority of 0 marks the slave as not able to perform the
# role of master, so a slave with priority of 0 will never be selected by
# Redis Sentinel for promotion.
#
# By default the priority is 100.
# 當主機crash的時候，在從機中選擇一臺作爲主機，數字越小，優先級越高
# 0 表示永遠不作爲主機，默認值是100
slave-priority 100
# It is possible for a master to stop accepting writes if there are less than
# N slaves connected, having a lag less or equal than M seconds.
#
# The N slaves need to be in "online" state.
#
# The lag in seconds, that must be <= the specified value, is calculated from
# the last ping received from the slave, that is usually sent every second.
#
# This option does not GUARANTEES that N replicas will accept the write, but
# will limit the window of exposure for lost writes in case not enough slaves
# are available, to the specified number of seconds.
#
# For example to require at least 3 slaves with a lag <= 10 seconds use:
#
# 當slave數量小於min-slaves-to-write，且延遲小於等於min-slaves-max-lag時，
# 主機停止寫入操作
# 0表示禁用
# 默認min-slaves-to-write爲0，即禁用。min-slaves-max-lag爲10
# min-slaves-to-write 3
# min-slaves-max-lag 10
#
# Setting one or the other to 0 disables the feature.
#
# By default min-slaves-to-write is set to 0 (feature disabled) and
# min-slaves-max-lag is set to 10.
################################## SECURITY ###################################
# Require clients to issue AUTH <PASSWORD> before processing any other
# commands. This might be useful in environments in which you do not trust
# others with access to the host running redis-server.
#
# This should stay commented out for backward compatibility and because most
# people do not need auth (e.g. they run their own servers).
#
# Warning: since Redis is pretty fast an outside user can try up to
# 150k passwords per second against a good box. This means that you should
# use a very strong password otherwise it will be very easy to break.
#
# redis密碼，默認不配置，即無密碼
# 這裏注意，如果設置了密碼，應該設置一個複雜度比較高的密碼
# 因爲redis的速度很快，每秒可以嘗試150k次的密碼測試，很容易對其進行暴力破解（跑碼）。
# 疑問：這裏爲什麼不設置一個針對主機的測試次數限制的，例如每10次，則禁止建立連接1個小時！
# requirepass foobared
# Command renaming.
#
# It is possible to change the name of dangerous commands in a shared
# environment. For instance the CONFIG command may be renamed into something
# hard to guess so that it will still be available for internal-use tools
# but not available for general clients.
#
# 命令重命名，將命令重命名爲另一個字符串標識
# 如果命令爲空串("")，則會徹底禁用該命令
# 命令重命名，會對寫AOF(Append of file)文件、slave從機造成一些問題
# Example:
#
# rename-command CONFIG b840fc02d524045429941cc15f59e41cb7be6c52
#
# It is also possible to completely kill a command by renaming it into
# an empty string:
#
# rename-command CONFIG ""
#
# Please note that changing the name of commands that are logged into the
# AOF file or transmitted to slaves may cause problems.
################################### LIMITS ####################################
# Set the max number of connected clients at the same time. By default
# this limit is set to 10000 clients, however if the Redis server is not
# able to configure the process file limit to allow for the specified limit
# the max number of allowed clients is set to the current file limit
# minus 32 (as Redis reserves a few file descriptors for internal uses).
#
# Once the limit is reached Redis will close all the new connections sending
# an error 'max number of clients reached'.
#
# 這隻redis的最大連接數目，默認設置爲10000個客戶端
# 當超過限制時，將段開新的連接，並響應“max number of clients reached”
# maxclients 10000
# Don't use more memory than the specified amount of bytes.
# When the memory limit is reached Redis will try to remove keys
# according to the eviction policy selected (see maxmemory-policy).
#
# If Redis can't remove keys according to the policy, or if the policy is
# set to 'noeviction', Redis will start to reply with errors to commands
# that would use more memory, like SET, LPUSH, and so on, and will continue
# to reply to read-only commands like GET.
#
# This option is usually useful when using Redis as an LRU cache, or to set
# a hard memory limit for an instance (using the 'noeviction' policy).
#
# WARNING: If you have slaves attached to an instance with maxmemory on,
# the size of the output buffers needed to feed the slaves are subtracted
# from the used memory count, so that network problems / resyncs will
# not trigger a loop where keys are evicted, and in turn the output
# buffer of slaves is full with DELs of keys evicted triggering the deletion
# of more keys, and so forth until the database is completely emptied.
#
# In short... if you have slaves attached it is suggested that you set a lower
# limit for maxmemory so that there is some free RAM on the system for slave
# output buffers (but this is not needed if the policy is 'noeviction').
#
# redis的最大內存限制，如果達到最大內存，會按照下面的maxmemory-policy進行清除
# 如果不能再清除或者maxmemory-policy爲noeviction，則對於需要增加空間的操作，將會返回錯誤
# maxmemory <bytes>
# MAXMEMORY POLICY: how Redis will select what to remove when maxmemory
# is reached. You can select among five behaviors:
#
# volatile-lru -> remove the key with an expire set using an LRU algorithm
# allkeys-lru -> remove any key accordingly to the LRU algorithm
# volatile-random -> remove a random key with an expire set
# allkeys-random -> remove a random key, any key
# volatile-ttl -> remove the key with the nearest expire time (minor TTL)
# noeviction -> don't expire at all, just return an error on write operations
#
# Note: with any of the above policies, Redis will return an error on write
# operations, when there are not suitable keys for eviction.
#
# At the date of writing this commands are: set setnx setex append
# incr decr rpush lpush rpushx lpushx linsert lset rpoplpush sadd
# sinter sinterstore sunion sunionstore sdiff sdiffstore zadd zincrby
# zunionstore zinterstore hset hsetnx hmset hincrby incrby decrby
# getset mset msetnx exec sort
#
# The default is:
#
# 內存刪除策略，默認volatile-lru，利用LRU算法，刪除過期的key
# maxmemory-policy volatile-lru
# LRU and minimal TTL algorithms are not precise algorithms but approximated
# algorithms (in order to save memory), so you can select as well the sample
# size to check. For instance for default Redis will check three keys and
# pick the one that was used less recently, you can change the sample size
# using the following configuration directive.
#
# LRU算法與最小TTL算法只是相對精確的算法，並不是絕對精確的算法
# 爲了更精確，可以設置樣本個數
# 比如設置3個樣本，redis會選取三個key，並選擇刪除那個上次使用時間最遠的
# maxmemory-samples 3
############################## 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).
#
# 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.
#
# Please check http://redis.io/topics/persistence for more information.
# 將對redis所有的操作都保存到AOF文件中
# 因爲dump.rdb是異步的，在下次快照到達之前，如果出現crash等問題，會造成數據丟失
# 而AOF文件時同步記錄的，所以會完整的恢復數據
appendonly no
# The name of the append only file (default: "appendonly.aof")
# AOF文件的名字
appendfilename "appendonly.aof"
# The fsync() call tells the Operating System to actually write data on disk
# instead to wait 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".
# redis的數據同步方式，三種
# no，redis本身不做同步，由OS來做。redis的速度會很快
# always，在每次寫操作之後，redis都進行同步，即寫入AOF文件。redis會變慢，但是數據更安全
# 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.
# redis的同步方式中，always和everysec，快照和寫AOF可能會執行大量的硬盤I/O操作，
# 而在一些Linux的配置中，redis會阻塞很久，而redis本身並沒有很好的解決這一問題。
# 爲了緩和這一問題，redis提供no-appendfsync-on-rewrite選項，
# 即當有另外一個進程在執行保存操作的時候，redis採用no的同步方式。
# 最壞情況下會有延遲30秒的同步延遲。
# 如果你覺得這樣做會有潛在危險，則請將該選項改爲yes。否則就保持默認值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文件
# 當AOF日誌文件大小增長到指定百分比時，redis會自動隱式調用BGREWRITEAOF來重寫AOF文件
# redis會記錄上次重寫AOF文件之後的大小，
# 如果當前文件大小增加了auto-aof-rewrite-percentage，則會觸發重寫AOF日誌功能
# 當然如果文件過小，比如小於auto-aof-rewrite-min-size這個大小，是不會觸發重寫AOF日誌功能的
# auto-aof-rewrite-percentage爲0時，禁用重寫功能
auto-aof-rewrite-percentage 100
auto-aof-rewrite-min-size 64mb
################################ LUA SCRIPTING ###############################
# Max execution time of a Lua script in milliseconds.
#
# If the maximum execution time is reached Redis will log that a script is
# still in execution after the maximum allowed time and will start to
# reply to queries with an error.
#
# When a long running script exceed the maximum execution time only the
# SCRIPT KILL and SHUTDOWN NOSAVE commands are available. The first can be
# used to stop a script that did not yet called write commands. The second
# is the only way to shut down the server in the case a write commands was
# already issue by the script but the user don't want to wait for the natural
# termination of the script.
#
# Set it to 0 or a negative value for unlimited execution without warnings.
# LUA腳本的最大執行時間（單位是毫秒），默認5000毫秒，即5秒
# 如果LUA腳本執行超過這個限制，可以調用SCRIPT KILL和SHUTDOWN NOSAVE命令。
# SCRIPT KILL可以終止腳本執行
# SHUTDOWN NOSAVE關閉服務，防止LUA腳本的寫操作發生
# 該值爲0或者負數，表示沒有限制時間
lua-time-limit 5000
################################## SLOW LOG ###################################
# The Redis Slow Log is a system to log queries that exceeded a specified
# execution time. The execution time does not include the I/O operations
# like talking with the client, sending the reply and so forth,
# but just the time needed to actually execute the command (this is the only
# stage of command execution where the thread is blocked and can not serve
# other requests in the meantime).
#
# You can configure the slow log with two parameters: one tells Redis
# what is the execution time, in microseconds, to exceed in order for the
# command to get logged, and the other parameter is the length of the
# slow log. When a new command is logged the oldest one is removed from the
# queue of logged commands.
# 記錄執行比較慢的命令
# 執行比較慢僅僅是指命令的執行時間，不包括客戶端的鏈接與響應等時間
# slowlog-log-slower-than 設定這個慢的時間，單位是微妙，即1000000表示1秒，0表示所有命令都記錄，負數表示不記錄
# slowlog-max-len表示記錄的慢命令的個數，超過限制，則最早記錄的命令會被移除
# 命令的長度沒有限制，但是會消耗內存，用SLOWLOG RESET來收回這些消耗的內存
# The following time is expressed in microseconds, so 1000000 is equivalent
# to one second. Note that a negative number disables the slow log, while
# a value of zero forces the logging of every command.
slowlog-log-slower-than 10000
# There is no limit to this length. Just be aware that it will consume memory.
# You can reclaim memory used by the slow log with SLOWLOG RESET.
slowlog-max-len 128
################################ LATENCY MONITOR ##############################
# The Redis latency monitoring subsystem samples different operations
# at runtime in order to collect data related to possible sources of
# latency of a Redis instance.
#
# Via the LATENCY command this information is available to the user that can
# print graphs and obtain reports.
#
# The system only logs operations that were performed in a time equal or
# greater than the amount of milliseconds specified via the
# latency-monitor-threshold configuration directive. When its value is set
# to zero, the latency monitor is turned off.
#
# By default latency monitoring is disabled since it is mostly not needed
# if you don't have latency issues, and collecting data has a performance
# impact, that while very small, can be measured under big load. Latency
# monitoring can easily be enalbed at runtime using the command
# "CONFIG SET latency-monitor-threshold <milliseconds>" if needed.
# 延遲監控器
# redis延遲監控子系統在運行時，會抽樣檢測可能導致延遲的不同操作
# 通過LATENCY命令可以打印相關信息和報告, 命令如下（摘自源文件註釋）：
# LATENCY SAMPLES: return time-latency samples for the specified event.
# LATENCY LATEST: return the latest latency for all the events classes.
# LATENCY DOCTOR: returns an human readable analysis of instance latency.
# LATENCY GRAPH: provide an ASCII graph of the latency of the specified event.
#
# 系統只記錄超過設定值的操作，單位是毫秒，0表示禁用該功能
# 可以通過命令“CONFIG SET latency-monitor-threshold <milliseconds>” 直接設置而不需要重啓redis
latency-monitor-threshold 0
############################# Event notification ##############################
# Redis can notify Pub/Sub clients about events happening in the key space.
# This feature is documented at http://redis.io/topics/keyspace-events
#
# For instance if keyspace events notification is enabled, and a client
# performs a DEL operation on key "foo" stored in the Database 0, two
# messages will be published via Pub/Sub:
#
# PUBLISH __keyspace@0__:foo del
# PUBLISH __keyevent@0__:del foo
#
# It is possible to select the events that Redis will notify among a set
# of classes. Every class is identified by a single character:
#
# K Keyspace events, published with __keyspace@<db>__ prefix.
# E Keyevent events, published with __keyevent@<db>__ prefix.
# g Generic commands (non-type specific) like DEL, EXPIRE, RENAME, ...
# $ String commands
# l List commands
# s Set commands
# h Hash commands
# z Sorted set commands
# x Expired events (events generated every time a key expires)
# e Evicted events (events generated when a key is evicted for maxmemory)
# A Alias for g$lshzxe, so that the "AKE" string means all the events.
#
# The "notify-keyspace-events" takes as argument a string that is composed
# by zero or multiple characters. The empty string means that notifications
# are disabled at all.
#
# Example: to enable list and generic events, from the point of view of the
# event name, use:
#
# notify-keyspace-events Elg
#
# Example 2: to get the stream of the expired keys subscribing to channel
# name __keyevent@0__:expired use:
#
# notify-keyspace-events Ex
#
# By default all notifications are disabled because most users don't need
# this feature and the feature has some overhead. Note that if you don't
# specify at least one of K or E, no events will be delivered.
# 事件通知，當事件發生時，redis可以通知Pub/Sub客戶端
# 空串表示禁用事件通知
# 注意：K和E至少要指定一個，否則不會有事件通知
notify-keyspace-events ""
############################### ADVANCED CONFIG ###############################
# Hashes are encoded using a memory efficient data structure when they have a
# small number of entries, and the biggest entry does not exceed a given
# threshold. These thresholds can be configured using the following directives.
# 當hash數目比較少，並且最大元素沒有超過給定值時，Hash使用比較有效的內存數據結構來存儲。
# 即ziplist的結構（壓縮的雙向鏈表），參考：http://blog.csdn.net/benbendy1984/article/details/7796956
hash-max-ziplist-entries 512
hash-max-ziplist-value 64
# Similarly to hashes, small lists are also encoded in a special way in order
# to save a lot of space. The special representation is only used when
# you are under the following limits:
# List配置同Hash
list-max-ziplist-entries 512
list-max-ziplist-value 64
# Sets have a special encoding in just one case: when a set is composed
# of just strings that happens to be integers in radix 10 in the range
# of 64 bit signed integers.
# The following configuration setting sets the limit in the size of the
# set in order to use this special memory saving encoding.
# Sets的元素如果全部是整數（10進制），且爲64位有符號整數，則採用特殊的編碼方式。
# 其元素個數限制配置如下：
set-max-intset-entries 512
# Similarly to hashes and lists, sorted sets are also specially encoded in
# order to save a lot of space. This encoding is only used when the length and
# elements of a sorted set are below the following limits:
# sorted set 同Hash和List
zset-max-ziplist-entries 128
zset-max-ziplist-value 64
# HyperLogLog sparse representation bytes limit. The limit includes the
# 16 bytes header. When an HyperLogLog using the sparse representation crosses
# this limit, it is converted into the dense representation.
#
# A value greater than 16000 is totally useless, since at that point the
# dense representation is more memory efficient.
#
# The suggested value is ~ 3000 in order to have the benefits of
# the space efficient encoding without slowing down too much PFADD,
# which is O(N) with the sparse encoding. The value can be raised to
# ~ 10000 when CPU is not a concern, but space is, and the data set is
# composed of many HyperLogLogs with cardinality in the 0 - 15000 range.
# 關於HyperLogLog的介紹：http://www.redis.io/topics/data-types-intro#hyperloglogs
# HyperLogLog稀疏表示限制設置，如果其值大於16000，則仍然採用稠密表示，因爲這時稠密表示更能有效使用內存
# 建議值爲3000
hll-sparse-max-bytes 3000
# Active rehashing uses 1 millisecond every 100 milliseconds of CPU time in
# order to help rehashing the main Redis hash table (the one mapping top-level
# keys to values). The hash table implementation Redis uses (see dict.c)
# performs a lazy rehashing: the more operation you run into a hash table
# that is rehashing, the more rehashing "steps" are performed, so if the
# server is idle the rehashing is never complete and some more memory is used
# by the hash table.
#
# The default is to use this millisecond 10 times every second in order to
# active rehashing the main dictionaries, freeing memory when possible.
#
# If unsure:
# use "activerehashing no" if you have hard latency requirements and it is
# not a good thing in your environment that Redis can reply form time to time
# to queries with 2 milliseconds delay.
#
# use "activerehashing yes" if you don't have such hard requirements but
# want to free memory asap when possible.
# 每100毫秒，redis將用1毫秒的時間對Hash表進行重新Hash。
# 採用懶惰Hash方式：操作Hash越多，則重新Hash的可能越多，若根本就不操作Hash，則不會重新Hash
# 默認每秒10次重新hash主字典，釋放可能釋放的內存
# 重新hash會造成延遲，如果對延遲要求較高，則設爲no，禁止重新hash。但可能會浪費很多內存
activerehashing yes
# The client output buffer limits can be used to force disconnection of clients
# that are not reading data from the server fast enough for some reason (a
# common reason is that a Pub/Sub client can't consume messages as fast as the
# publisher can produce them).
#
# The limit can be set differently for the three different classes of clients:
#
# normal -> normal clients including MONITOR clients
# slave -> slave clients
# pubsub -> clients subscribed to at least one pubsub channel or pattern
#
# The syntax of every client-output-buffer-limit directive is the following:
#
# 客戶端輸出緩衝區限制，當客戶端從服務端的讀取速度不夠快時，則強制斷開
# 三種不同的客戶端類型：normal、salve、pubsub，語法如下：
# client-output-buffer-limit <class> <hard limit> <soft limit> <soft seconds>
#
# A client is immediately disconnected once the hard limit is reached, or if
# the soft limit is reached and remains reached for the specified number of
# seconds (continuously).
# So for instance if the hard limit is 32 megabytes and the soft limit is
# 16 megabytes / 10 seconds, the client will get disconnected immediately
# if the size of the output buffers reach 32 megabytes, but will also get
# disconnected if the client reaches 16 megabytes and continuously overcomes
# the limit for 10 seconds.
#
# By default normal clients are not limited because they don't receive data
# without asking (in a push way), but just after a request, so only
# asynchronous clients may create a scenario where data is requested faster
# than it can read.
#
# Instead there is a default limit for pubsub and slave clients, since
# subscribers and slaves receive data in a push fashion.
#
# Both the hard or the soft limit can be disabled by setting them to zero.
# 當達到硬限制，或者達到軟限制且持續了算限制秒數，則立即與客戶端斷開
# 限制設爲0表示禁止該功能
# 普通用戶默認不限制
client-output-buffer-limit normal 0 0 0
client-output-buffer-limit slave 256mb 64mb 60
client-output-buffer-limit pubsub 32mb 8mb 60
# Redis calls an internal function to perform many background tasks, like
# closing connections of clients in timeout, purging expired keys that are
# never requested, and so forth.
#
# Not all tasks are performed with the same frequency, but Redis checks for
# tasks to perform accordingly to the specified "hz" value.
#
# By default "hz" is set to 10. Raising the value will use more CPU when
# Redis is idle, but at the same time will make Redis more responsive when
# there are many keys expiring at the same time, and timeouts may be
# handled with more precision.
#
# The range is between 1 and 500, however a value over 100 is usually not
# a good idea. Most users should use the default of 10 and raise this up to
# 100 only in environments where very low latency is required.
# redis調用內部函數執行的後臺任務的頻率
# 後臺任務比如：清除過期數據、客戶端超時鏈接等
# 默認爲10，取值範圍1~500,
# 對延遲要求很低的可以設置超過100以上
hz 10
# When a child rewrites the AOF file, if the following option is enabled
# the file will be fsync-ed every 32 MB of data generated. This is useful
# in order to commit the file to the disk more incrementally and avoid
# big latency spikes.
# 當修改AOF文件時，該設置爲yes，則每生成32MB的數據，就進行同步
aof-rewrite-incremental-fsync yes