注意不同版本之间有一点点区别，如日志级别# redis 配置文件示例 # 当你需要为某个配置项指定内存大小的时候，必须要带上单位，# 通常的格式就是 1k 5gb 4m 等酱紫：## 1k => 1000 bytes# 1kb => 1024 bytes# 1m => 1000000 bytes# 1mb => 1024*1024 bytes# 1g => 1000000000 bytes# 1gb => 1024*1024*1024 bytes## 单位是不区分大小写的，你写 1K 5GB 4M 也行 ################################## INCLUDES ################################### # 假如说你有一个可用于所有的 redis server 的标准配置模板，# 但针对某些 server 又需要一些个性化的设置，# 你可以使用 include 来包含一些其他的配置文件，这对你来说是非常有用的。## 但是要注意哦，include 是不能被 config rewrite 命令改写的# 由于 redis 总是以最后的加工线作为一个配置指令值，所以你最好是把 include 放在这个文件的最前面，# 以避免在运行时覆盖配置的改变，相反，你就把它放在后面（外国人真啰嗦）。## include /path/to/local.conf# include /path/to/other.conf ################################ 常用 ##################################### # 默认情况下 redis 不是作为守护进程运行的，如果你想让它在后台运行，你就把它改成 yes。# 当redis作为守护进程运行的时候，它会写一个 pid 到 /var/run/redis.pid 文件里面。daemonize no # 当redis作为守护进程运行的时候，它会把 pid 默认写到 /var/run/redis.pid 文件里面，# 但是你可以在这里自己制定它的文件位置。pidfile /var/run/redis.pid # 监听端口号，默认为 6379，如果你设为 0 ，redis 将不在 socket 上监听任何客户端连接。port 6379 # TCP 监听的最大容纳数量## 在高并发的环境下，你需要把这个值调高以避免客户端连接缓慢的问题。# linux 内核会一声不响的把这个值缩小成 /PRoc/sys/net/core/somaxconn 对应的值，# 所以你要修改这两个值才能达到你的预期。tcp-backlog 511 # 默认情况下，redis 在 server 上所有有效的网络接口上监听客户端连接。# 你如果只想让它在一个网络接口上监听，那你就绑定一个ip或者多个IP。## 示例，多个IP用空格隔开:## bind 192.168.1.100 10.0.0.1# bind 127.0.0.1 # 指定 unix socket 的路径。## unixsocket /tmp/redis.sock# unixsocketperm 755 # 指定在一个 client 空闲多少秒之后关闭连接（0 就是不管它）timeout 0 # tcp 心跳包。## 如果设置为非零，则在与客户端缺乏通讯的时候使用 SO_KEEPALIVE 发送 tcp acks 给客户端。# 这个之所有有用，主要由两个原因：## 1) 防止死的 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.## A reasonable value for this option is 60 seconds.# 推荐一个合理的值就是60秒tcp-keepalive 0 # 定义日志级别。# 可以是下面的这些值：# debug (适用于开发或测试阶段)# verbose (many rarely useful info, but not a mess like the debug level)# notice (适用于生产环境)# warning (仅仅一些重要的消息被记录)loglevel notice # 指定日志文件的位置logfile "" # 要想把日志记录到系统日志，就把它改成 yes，# 也可以可选择性的更新其他的syslog 参数以达到你的要求# syslog-enabled no # 设置 syslog 的 identity。# syslog-ident redis # 设置 syslog 的 facility，必须是 USER 或者是 LOCAL0-LOCAL7 之间的值。# syslog-facility local0 # 设置数据库的数目。# 默认数据库是 DB 0，你可以在每个连接上使用 select <dbid> 命令选择一个不同的数据库，# 但是 dbid 必须是一个介于 0 到 databasees - 1 之间的值databases 16 ################################ 快照 ################################## 存 DB 到磁盘：## 格式：save <间隔时间（秒）> <写入次数>## 根据给定的时间间隔和写入次数将数据保存到磁盘## 下面的例子的意思是：# 900 秒内如果至少有 1 个 key 的值变化，则保存# 300 秒内如果至少有 10 个 key 的值变化，则保存# 60 秒内如果至少有 10000 个 key 的值变化，则保存# # 注意：你可以注释掉所有的 save 行来停用保存功能。# 也可以直接一个空字符串来实现停用：# save "" save 900 1save 300 10save 60 10000 # 默认情况下，如果 redis 最后一次的后台保存失败，redis 将停止接受写操作，# 这样以一种强硬的方式让用户知道数据不能正确的持久化到磁盘，# 否则就会没人注意到灾难的发生。## 如果后台保存进程重新启动工作了，redis 也将自动的允许写操作。## 然而你要是安装了靠谱的监控，你可能不希望 redis 这样做，那你就改成 no 好了。stop-writes-on-bgsave-error yes # 是否在 dump .rdb 数据库的时候使用 LZF 压缩字符串# 默认都设为 yes# 如果你希望保存子进程节省点 cpu ，你就设置它为 no ，# 不过这个数据集可能就会比较大rdbcompression yes # 是否校验rdb文件rdbchecksum yes # 设置 dump 的文件位置dbfilename dump.rdb # 工作目录# 例如上面的 dbfilename 只指定了文件名，# 但是它会写入到这个目录下。这个配置项一定是个目录，而不能是文件名。dir ./ ################################# 主从复制 ################################# # 主从复制。使用 slaveof 来让一个 redis 实例成为另一个reids 实例的副本。# 注意这个只需要在 slave 上配置。## slaveof <masterip> <masterport> # 如果 master 需要密码认证，就在这里设置# masterauth <master-passWord> # 当一个 slave 与 master 失去联系，或者复制正在进行的时候，# slave 可能会有两种表现：## 1) 如果为 yes ，slave 仍然会应答客户端请求，但返回的数据可能是过时，# 或者数据可能是空的在第一次同步的时候## 2) 如果为 no ，在你执行除了 info he salveof 之外的其他命令时，# slave 都将返回一个 "SYNC with master in progress" 的错误，#slave-serve-stale-data yes # 你可以配置一个 slave 实体是否接受写入操作。# 通过写入操作来存储一些短暂的数据对于一个 slave 实例来说可能是有用的，# 因为相对从 master 重新同步数而言，据数据写入到 slave 会更容易被删除。# 但是如果客户端因为一个错误的配置写入，也可能会导致一些问题。## 从 redis 2.6 版起，默认 slaves 都是只读的。## 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.# 注意：只读的 slaves 没有被设计成在 internet 上暴露给不受信任的客户端。# 它仅仅是一个针对误用实例的一个保护层。slave-read-only yes # Slaves 在一个预定义的时间间隔内发送 ping 命令到 server 。# 你可以改变这个时间间隔。默认为 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 大## 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.repl-disable-tcp-nodelay no # 设置主从复制容量大小。这个 backlog 是一个用来在 slaves 被断开连接时# 存放 slave 数据的 buffer，所以当一个 slave 想要重新连接，通常不希望全部重新同步，# 只是部分同步就够了，仅仅传递 slave 在断开连接时丢失的这部分数据。## The biggest the replication backlog, the longer the time the slave can be# disconnected and later be able to perform a partial resynchronization.# 这个值越大，salve 可以断开连接的时间就越长。## The backlog is only allocated once there is at least a slave connected.## 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.# 在某些时候，master 不再连接 slaves，backlog 将被释放。## A value of 0 means to never release the backlog.# 如果设置为 0 ，意味着绝不释放 backlog 。## repl-backlog-ttl 3600 # 当 master 不能正常工作的时候，Redis Sentinel 会从 slaves 中选出一个新的 master，# 这个值越小，就越会被优先选中，但是如果是 0 ， 那是意味着这个 slave 不可能被选中。## 默认优先级为 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:## 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. ################################## 安全 ################################### # 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.# # 设置认证密码# 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.## 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. ################################### 限制 #################################### # 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).## 一旦达到最大限制，redis 将关闭所有的新连接# 并发送一个‘max number of clients reached’的错误。## maxclients 10000 # 如果你设置了这个值，当缓存的数据容量达到这个值， redis 将根据你选择的# eviction 策略来移除一些 keys。## 如果 redis 不能根据策略移除 keys ，或者是策略被设置为 ‘noeviction’，# redis 将开始响应错误给命令，如 set，lpush 等等，# 并继续响应只读的命令，如 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').## 最大使用内存# maxmemory <bytes> # 最大内存策略，你有 5 个选择。# # volatile-lru -> remove the key with an expire set using an LRU algorithm# volatile-lru -> 使用 LRU 算法移除包含过期设置的 key 。# allkeys-lru -> remove any key accordingly to the LRU algorithm# allkeys-lru -> 根据 LRU 算法移除所有的 key 。# 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# noeviction -> 不让任何 key 过期，只是给写入操作返回一个错误# # 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:## maxmemory-policy noeviction # LRU and minimal TTL algorithms are not precise algorithms but approximated# algorithms (in order to save memory), so you can tune it for speed or# accuracy. For default Redis will check five keys and pick the one that was# used less recently, you can change the sample size using the following# configuration directive.## The default of 5 produces good enough results. 10 Approximates very closely# true LRU but costs a bit more CPU. 3 is very fast but not very accurate.## maxmemory-samples 5 ############################## 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. appendonly no # The name of the append only file (default: "appendonly.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". # appendfsync alwaysappendfsync 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. 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. auto-aof-rewrite-percentage 100auto-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-time-limit 5000 ################################ REDIS 集群 ################################# 启用或停用集群# cluster-enabled yes # Every cluster node has a cluster configuration file. This file is not# intended to be edited by hand. It is created and updated by Redis nodes.# Every Redis Cluster node requires a different cluster configuration file.# Make sure that instances running in the same system does not have# overlapping cluster configuration file names.## cluster-config-file nodes-6379.conf # Cluster node timeout is the amount of milliseconds a node must be unreachable # for it to be considered in failure state.# Most other internal time limits are multiple of the node timeout.## cluster-node-timeout 15000 # A slave of a failing master will avoid to start a failover if its data# looks too old.## There is no simple way for a slave to actually have a exact measure of# its "data age", so the following two checks are performed:## 1) If there are multiple slaves able to failover, they exchange messages# in order to try to give an advantage to the slave with the best# replication offset (more data from the master processed).# Slaves will try to get their rank by offset, and apply to the start# of the failover a delay proportional to their rank.## 2) Every single slave computes the time of the last interaction with# its master. This can be the last ping or command received (if the master# is still in the "connected" state), or the time that elapsed since the# disconnection with the master (if the replication link is currently down).# If the last interaction is too old, the slave will not try to failover# at all.## The point "2" can be tuned by user. Specifically a slave will not perform# the failover if, since the last interaction with the master, the time# elapsed is greater than:## (node-timeout * slave-validity-factor) + repl-ping-slave-period## So for example if node-timeout is 30 seconds, and the slave-validity-factor# is 10, and assuming a default repl-ping-slave-period of 10 seconds, the# slave will not try to failover if it was not able to talk with the master# for longer than 310 seconds.## A large slave-validity-factor may allow slaves with too old data to failover# a master, while a too small value may prevent the cluster from being able to# elect a slave at all.## For maximum availability, it is possible to set the slave-validity-factor# to a value of 0, which means, that slaves will always try to failover the# master regardless of the last time they interacted with the master.# (However they'll always try to apply a delay proportional to their# offset rank).## Zero is the only value able to guarantee that when all the partitions heal# the cluster will always be able to continue.## cluster-slave-validity-factor 10 # Cluster slaves are able to migrate to orphaned masters, that are masters# that are left without working slaves. This improves the cluster ability# to resist to failures as otherwise an orphaned master can't be failed over# in case of failure if it has no working slaves.## Slaves migrate to orphaned masters only if there are still at least a# given number of other working slaves for their old master. This number# is the "migration barrier". A migration barrier of 1 means that a slave# will migrate only if there is at least 1 other working slave for its master# and so forth. It usually reflects the number of slaves you want for every# master in your cluster.## Default is 1 (slaves migrate only if their masters remain with at least# one slave). To disable migration just set it to a very large value.# A value of 0 can be set but is useful only for debugging and dangerous# in production.## cluster-migration-barrier 1 # In order to setup your cluster make sure to read the documentation# available at http://redis.io web site. ################################## 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. # 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 ############################# 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.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-max-ziplist-entries 512hash-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-max-ziplist-entries 512list-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.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:zset-max-ziplist-entries 128zset-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.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.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# slave -> slave clients and MONITOR clients# pubsub -> clients subscribed to at least one pubsub channel or pattern## The syntax of every client-output-buffer-limit directive is the following:## 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.client-output-buffer-limit normal 0 0 0client-output-buffer-limit slave 256mb 64mb 60client-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.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-rewrite-incremental-fsync yes配置文件参数说明:
1. Redis默认不是以守护进程的方式运行，可以通过该配置项修改，使用yes启用守护进程
daemonize no
2. 当Redis以守护进程方式运行时，Redis默认会把pid写入/var/run/redis.pid文件，可以通过pidfile指定
pidfile /var/run/redis.pid
3. 指定Redis监听端口，默认端口为6379，作者在自己的一篇博文中解释了为什么选用6379作为默认端口，因为6379在手机按键上MERZ对应的号码，而MERZ取自意大利歌女Alessia Merz的名字
port 6379
4. 绑定的主机地址
bind 127.0.0.1
5.当 客户端闲置多长时间后关闭连接，如果指定为0，表示关闭该功能
timeout 300
6. 指定日志记录级别，Redis总共支持四个级别：debug、verbose、notice、warning，默认为verbose
loglevel verbose
7. 日志记录方式，默认为标准输出，如果配置Redis为守护进程方式运行，而这里又配置为日志记录方式为标准输出，则日志将会发送给/dev/null
logfile stdout
8. 设置数据库的数量，默认数据库为0，可以使用SELECT <dbid>命令在连接上指定数据库id
databases 16
9. 指定在多长时间内，有多少次更新操作，就将数据同步到数据文件，可以多个条件配合
save <seconds> <changes>
Redis默认配置文件中提供了三个条件：
save 900 1
save 300 10
save 60 10000
分别表示900秒（15分钟）内有1个更改，300秒（5分钟）内有10个更改以及60秒内有10000个更改。
10. 指定存储至本地数据库时是否压缩数据，默认为yes，Redis采用LZF压缩，如果为了节省CPU时间，可以关闭该选项，但会导致数据库文件变的巨大
rdbcompression yes
11. 指定本地数据库文件名，默认值为dump.rdb
dbfilename dump.rdb
12. 指定本地数据库存放目录
dir ./
13. 设置当本机为slav服务时，设置master服务的IP地址及端口，在Redis启动时，它会自动从master进行数据同步
slaveof <masterip> <masterport>
14. 当master服务设置了密码保护时，slav服务连接master的密码
masterauth <master-password>
15. 设置Redis连接密码，如果配置了连接密码，客户端在连接Redis时需要通过AUTH <password>命令提供密码，默认关闭
requirepass foobared
16. 设置同一时间最大客户端连接数，默认无限制，Redis可以同时打开的客户端连接数为Redis进程可以打开的最大文件描述符数，如果设置 maxclients 0，表示不作限制。当客户端连接数到达限制时，Redis会关闭新的连接并向客户端返回max number of clients reached错误信息
maxclients 128
17. 指定Redis最大内存限制，Redis在启动时会把数据加载到内存中，达到最大内存后，Redis会先尝试清除已到期或即将到期的Key，当此方法处理 后，仍然到达最大内存设置，将无法再进行写入操作，但仍然可以进行读取操作。Redis新的vm机制，会把Key存放内存，Value会存放在swap区
maxmemory <bytes>
18. 指定是否在每次更新操作后进行日志记录，Redis在默认情况下是异步的把数据写入磁盘，如果不开启，可能会在断电时导致一段时间内的数据丢失。因为 redis本身同步数据文件是按上面save条件来同步的，所以有的数据会在一段时间内只存在于内存中。默认为no
appendonly no
19. 指定更新日志文件名，默认为appendonly.aof
appendfilename appendonly.aof
20. 指定更新日志条件，共有3个可选值： no：表示等操作系统进行数据缓存同步到磁盘（快） always：表示每次更新操作后手动调用fsync()将数据写到磁盘（慢，安全） everysec：表示每秒同步一次（折衷，默认值）
appendfsync everysec
21. 指定是否启用虚拟内存机制，默认值为no，简单的介绍一下，VM机制将数据分页存放，由Redis将访问量较少的页即冷数据swap到磁盘上，访问多的页面由磁盘自动换出到内存中（在后面的文章我会仔细分析Redis的VM机制）
vm-enabled no
22. 虚拟内存文件路径，默认值为/tmp/redis.swap，不可多个Redis实例共享
vm-swap-file /tmp/redis.swap
23. 将所有大于vm-max-memory的数据存入虚拟内存,无论vm-max-memory设置多小,所有索引数据都是内存存储的(Redis的索引数据 就是keys),也就是说,当vm-max-memory设置为0的时候,其实是所有value都存在于磁盘。默认值为0
vm-max-memory 0
24. Redis swap文件分成了很多的page，一个对象可以保存在多个page上面，但一个page上不能被多个对象共享，vm-page-size是要根据存储的 数据大小来设定的，作者建议如果存储很多小对象，page大小最好设置为32或者64bytes；如果存储很大大对象，则可以使用更大的page，如果不 确定，就使用默认值
vm-page-size 32
25. 设置swap文件中的page数量，由于页表（一种表示页面空闲或使用的bitmap）是在放在内存中的，，在磁盘上每8个pages将消耗1byte的内存。
vm-pages 134217728
26. 设置访问swap文件的线程数,最好不要超过机器的核数,如果设置为0,那么所有对swap文件的操作都是串行的，可能会造成比较长时间的延迟。默认值为4
vm-max-threads 4
27. 设置在向客户端应答时，是否把较小的包合并为一个包发送，默认为开启
glueoutputbuf yes
28. 指定在超过一定的数量或者最大的元素超过某一临界值时，采用一种特殊的哈希算法
hash-max-zipmap-entries 64
hash-max-zipmap-value 512
29. 指定是否激活重置哈希，默认为开启（后面在介绍Redis的哈希算法时具体介绍）
activerehashing yes
30. 指定包含其它的配置文件，可以在同一主机上多个Redis实例之间使用同一份配置文件，而同时各个实例又拥有自己的特定配置文件
include /path/to/local.conf
----------------------
Redis配置文件被分成几大块区域，分别是:
1.通用(general)
2.快照(snapshotting)
3.复制(replication)
4.安全(security)
5.限制(limits)
6.追加模式(append only mode)
7.LUA脚本(lua scripting)
8.Redis集群(redis cluster)
9.慢日志(slow log)
10.延迟监控(latency monitor)
11.事件通知(event notification)
12.高级配置(advanced config)
注: INCLUDES配置:当机器不只存在1个Redis实例时，可以实现每个Redis实例的"个性化"配置，此时，可以将这些实例的共有配置写到redis.conf中，而个性化的配置写到由include配置路径指定的文件中。
1. 通用(general):
############################ GENERAL #################################daemonize no ##是否以后台daemon方式运行(默认为no)pidfile /var/run/redis/redis.pid ##Pid文件位置port 6379 ##监听端口tcp-backlog 511 ##客户端连接队列值, 在高并发的环境中，为避免慢客户端的连接问题，需要设置一个高速后台日志bind 127.0.0.1 ##指定redis所响应的连接请求(默认响应本机所有网卡的连接请求)timeout 0 ##请求超时时间(0表示永不关闭)tcp-keepalive 0 ##TCP存活检测(单位为秒,0表示不进行检测)loglevel notice ##log信息级别(分四级，即debug、verbose、notice、warning)logfile /var/log/redis/redis.log ##log文件位置，如设置为[logfile ""]空字符串，则redis会将日志输出到标准输出，被写到/dev/null中databases 16 ##开启数据库数量(默认数据库是编号为0的数据库,可使用select <DBid>来选择相应数据库)2. 快照(snapshotting) ----主要涉及的是redis的RDB持久化相关的配置
save * *: 保存快照的频率,第一个*表示多长时间,第二个*表示执行多少次写操作。在一定时间内执行一定数量的写操作时，自动保存快照，可设置多个条件。如想禁用RDB持久化策略，不设置任何save指令即以，或设置[save ""]
########################## SNAPSHOTTING #############################save 900 1 ##每15分钟且至少有1个key改变，就触发一次持久化save 300 10 ##每5分钟且至少有10个key改变，就触发一次持久化save 60 10000 ##每60秒至少有10000个key改变，就触发一次持久化stop-writes-on-bgsave-error yes ##redis持久化数据到磁盘时如出现失败，默认redis会停止接受所有的写请求rdbcompression yes ##是否使用压缩rdbchecksum yes ##是否使用CRC64算法来进行数据校验dbfilename dump.rdb ##设置数据快照文件名(只是文件名,不包括目录)dir /var/lib/redis/ ##设置数据快照的保存目录(这个是目录)3. 复制(replication)
############################### REPLICATION ##########################
通过slaveof配置项可控制某一个redis作为另一个redis的从服务器，通过指定IP和端口来定位到主redis的位置
# slaveof <masterip> <masterport>如主redis设置验证密码(使用requirepass设置)，则需在从redis的配置中使用masterauth来设置校验密码，否则主redis会拒绝从redis的访问请求
# masterauth <master-password>从redis失去与主redis的连接，或者主从同步正在进行时，redis对外部发来的访问请求的两种处理选择:
选择1:设置为yes(默认)，从redis仍会继续响应客户端的读写请求
选择2:设置为no，从redis会对客户端的请求返回“SYNC with master in progress”(例外:当客户端发来INFO请求和SLAVEOF请求，从redis还是会进行处理)
slave-serve-stale-data yes slave-read-only yes ##设置从redis只读复制同步策略：磁盘或者socket
新的从redis上线或主redis重新上线时应做数据全同步。需要将一个新的RDB文件dump出来，然后从主redis传到从redis。有两种情况：
1. 基于硬盘(disk-backed):主redis创建一个新进程dump RDB，之后由父进程(即主进程)增量传给从redis
2. 基于socket(diskless):主redis创建一个新进程直接dump RDB到从redis的socket，不经过主进程，不经过硬盘
如基于硬盘，RDB文件创建后，一旦创建完毕，可以同时服务更多从redis；如基于socket，新的从redis加入后，需进行排队(如超出repl-diskless-sync-delay设定时时)；当用diskless时，主redis等待repl-diskless-sync-delay设定的秒数后，如无新的从redis加入，就直接传，后来的需排队等待。(默认用disk-based)
repl-diskless-sync norepl-diskless-sync-delay 5 ##每五秒传输一次(需开启diskless)# repl-ping-slave-period 10 ##设置从redis向主redis发出PING包的周期(默认10秒)在主从同步时，可能在这些情况下会有超时发生:
1. 以从redis的角度来看，当有大规模IO传输时。
2. 以从redis的角度来看，当数据传输或PING时，主redis超时
3. 以主redis的角度来看，在回复从redis的PING时，从redis超时
用户可以设置上述超时的时限，不过要确保这个时限比repl-ping-slave-period的值要大，否则每次主redis都会认为从redis超时。
# repl-timeout 60设置主从同步时是否禁用TCP_NODELAY。如开启TCP_NODELAY，主redis会使用更少的TCP包和更少的带宽来向从redis传输数据，但可能会增加同步延迟(40ms)。如关闭TCP_NODELAY，那数据同步的延迟时间会降低，但会消耗更多的带宽
repl-disable-tcp-nodelay no设置同步队列长度。队列长度（backlog)是主redis中的一个缓冲区，在与从redis断开连接期间，主redis会用这个缓冲区来缓存应该发给从redis的数据。这样，当从redis重新连接上后，就不必重新全量同步数据，只需要同步这部分增量数据即可
# repl-backlog-size 1mb设置主redis清理缓冲队列等待的时间长度(设置为0表示永不清理,默认为1个小时)
# repl-backlog-ttl 3600slave-priority 100 ##设置从redis优先级，编号越小，优先级越高(默认100)如主redis发现有超过M个从redis的连接延时大于N秒，那么主redis就停止接受外来的写请求
# min-slaves-to-write 3# min-slaves-max-lag 10假如有大于等于3个从redis的连接延迟大于10秒，那么主redis就不再接受外部的写请求。上述两个配置中有一个被置为0，则这个特性将被关闭
4. 安全(security)
############################# SECURITY ###################################设置redis客户端在向redis-server发送请求之前，先进行密码验证。# requirepass foobared ##设置密码为"foobared"# rename-command CONFIG b840fc02d524045429941...... ##对redis指令进行更名# rename-command CONFIG "" ##禁用CONFIG命令5. 限制(limits)
############################### LIMITS ################################# maxclients 10000 ##设置redis可以同时与多少个客户端进行连接(默认为10000个客户端)# maxmemory <bytes>设置redis可使用的内存量。一旦到达内存使用上限，redis将会试图移除内部数据，移除规则可以通过maxmemory-policy来指定。如redis无法根据移除规则来移除内存中的数据，或者我们设置了“不允许移除”，那么redis则会针对那些需要申请内存的指令返回错误信息
如果你的redis是主redis，那么在设置内存使用上限时，需要在系统中留出一些内存空间给同步队列缓存，只有在设置的是“不移除”的情况下，才不用考虑这个因素。
对于内存移除规则来说，redis提供了多达6种的移除规则。他们是:
1. volatile-lru：使用LRU算法移除过期集合中的key
2. allkeys-lru：使用LRU算法移除key
3. volatile-random：在过期集合中移除随机的key
4. allkeys-random：移除随机的key
5. volatile-ttl：移除那些TTL值最小的key，即那些最近才过期的key。
6. noeviction：不进行移除。针对写操作，只是返回错误信息。(默认规则)
无论使用上述哪一种移除规则，如果没有合适的key可以移除的话，redis都会针对写请求返回错误信息。
# maxmemory-policy noeviction ##不进行移除# maxmemory-samples 5 ##设置LRU算法的样本数6. 追加模式(append only mode)
########################## APPEND ONLY MODE ###########################appendonly on ##打开AOF功能appendfilename "appendonly.aof" ##设置AOF文件的名称AOF持久化策略，fsync()调用，用来告诉操作系统立即将缓存的指令写入磁盘，redis支持三种不同的模式:
1. always:每次写请求都强制调用fsync，该模式下，redis会相对较慢，但数据最安全
2. everysec:每秒调用一次fsync
3. on:不调用fsync等待系统自己同步[fsync是指把缓存中的写指令记录到磁盘中]
appendfsync everysec ##每秒调用一次fsync当BGSAVE或BGWRITEAOF运行时，fsync()在主进程中的调用会被阻止。这意味着当另一路进程正在对AOF文件进行重构时，redis的持久化功能就失效了，就像设置了“appendsync none”一样。 如果redis有时延问题， 那么将选项设置为yes。 否则请保持no，因为这是保证数据完整性的最安全的选择。
no-appendfsync-on-rewrite no允许redis自动重写aof。当aof增长到一定规模时，redis会隐式调用BGREWRITEAOF来重写log文件，以缩减文件体积。redis是这样工作的:redis会记录上次重写时的aof大小。如redis自启动至今还没有进行过重写，那么启动时aof文件的大小会被作为基准值。该基准值会和当前的aof大小进行比较。如当前aof大小超出所设置的增长比例，则会触发重写。另外还需要设置一个最小大小，是为了防止在aof很小时就触发重写。如设置auto-aof-rewrite-percentage为0，则会关闭此重写功能。
auto-aof-rewrite-percentage 100auto-aof-rewrite-min-size 64mbaof-load-truncated yes ##当aof文件被损坏时,redis将返回错误并退出7. LUA脚本(lua scripting)
############################ LUA SCRIPTING #########################lua-time-limit 5000 ##设置lua脚本最大运行时间(默认毫秒，设置为0或负数，既不会报错也无时间限制)8. Redis集群(redis cluster)
############################ REDIS CLUSTER ########################### cluster-enabled yes ##开启redis集群# cluster-config-file nodes-6379.conf ##集群配置文件(启动自动生成)# cluster-node-timeout 15000 ##节点互联超时的阀值# cluster-slave-validity-factor 10 ##slave节点检测因素，开始failover的超时时限是通过factor与timeout的乘积来确定的# cluster-migration-barrier 1 ##设置master只有在关联多少slave时才会触发迁移过程# cluster-require-full-coverage yes ##集群各节点在检测到至少一个hash槽位遗漏的情况下将停止处理查询请求。如集群部分节点宕机(例如部分hash槽位没有被分配)会造成整个集群不可用，直到所有槽位均被分配时才会自动恢复为可用状态9. 慢日志(slow log)
############################### SLOW LOG ###############################redis慢日志是指一个系统进行日志查询超过了指定时长。这个时长不包括IO操作，如与客户端的交互、发送响应内容等，而仅包括实际执行查询命令的时间。针对慢日志，可设置两个参数，一个是执行时长，单位是微秒;另一个是慢日志的长度。当一个新的命令被写入日志时，最老的一条会从命令日志队列中被移除。slowlog-log-slower-than 10000 ##设置执行时长为10000微秒(单位为微秒，负数表示禁用慢日志功能，而0则表示强制记录每一个命令)slowlog-max-len 128 ##设置慢日志最大长度10. 延迟监控(latency monitor)
############################# LATENCY MONITOR ####################latency-monitor-threshold 0 ##用LATENCY打印redis实例在跑命令时的耗时图表，只记录大于等于所设置值的操作(0表示关闭监控)11. 事件通知(event notification) ----向客户端通知某些事件的发生
########################## EVENT NOTIFICATION #######################notify-keyspace-events "" ##通知pub/sub客户端关于key空间的变化(默认关闭)12. 高级配置(advanced config)
############################# ADVANCED CONFIG ##########################有关哈希数据结构的配置项hash-max-ziplist-entries 512hash-max-ziplist-value 64##有关列表数据结构的配置项list-max-ziplist-entries 512list-max-ziplist-value 64##有关集合数据结构的配置项set-max-intset-entries 512##有关有序集合数据结构的配置项zset-max-ziplist-entries 128zset-max-ziplist-value 64##有关HyperLogLog字节限制的配置项hll-sparse-max-bytes 3000##关于是否需要再哈希的配置项activerehashing yes##关于客户端输出缓冲的控制项client-output-buffer-limit normal 0 0 0client-output-buffer-limit slave 256mb 64mb 60client-output-buffer-limit pubsub 32mb 8mb 60##有关频率的配置项hz 10##有关重写aof的配置项aof-rewrite-incremental-fsync yes
新闻热点
疑难解答
