Redis配置文件

  1. # 当配置中需要配置内存大小时，可以使用 1k, 5GB, 4M 等类似的格式，其转换方式如下(不区分大小写)
  2. #
  3. # 1k => 1000 bytes
  4. # 1kb => 1024 bytes
  5. # 1m => 1000000 bytes
  6. # 1mb => 1024*1024 bytes
  7. # 1g => 1000000000 bytes
  8. # 1gb => 1024*1024*1024 bytes
  9. #
  10. # 内存配置大小写是一样的.比如 1gb 1Gb 1GB 1gB
  13. # daemonize no 默认情况下，redis不是在后台运行的，如果需要在后台运行，把该项的值更改为yes
  14. daemonize yes
  16. # 当redis在后台运行的时候，Redis默认会把pid文件放在/var/run/redis.pid，你可以配置到其他地址。
  17. # 当运行多个redis服务时，需要指定不同的pid文件和端口
  18. pidfile /var/run/redis.pid
  20. # 指定redis运行的端口，默认是6379
  21. port 6379
  23. # 指定redis只接收来自于该IP地址的请求，如果不进行设置，那么将处理所有请求，
  24. # 在生产环境中最好设置该项
  25. # bind 127.0.0.1
  27. # Specify the path for the unix socket that will be used to listen for
  28. # incoming connections. There is no default, so Redis will not listen
  29. # on a unix socket when not specified.
  30. #
  31. # unixsocket /tmp/redis.sock
  32. # unixsocketperm 755
  34. # 设置客户端连接时的超时时间，单位为秒。当客户端在这段时间内没有发出任何指令，那么关闭该连接
  35. # 0是关闭此设置
  36. timeout 0
  38. # 指定日志记录级别
  39. # Redis总共支持四个级别：debug、verbose、notice、warning，默认为verbose
  40. # debug 记录很多信息，用于开发和测试
  41. # varbose 有用的信息，不像debug会记录那么多
  42. # notice 普通的verbose，常用于生产环境
  43. # warning 只有非常重要或者严重的信息会记录到日志
  44. loglevel debug
  46. # 配置log文件地址
  47. # 默认值为stdout，标准输出，若后台模式会输出到/dev/null
  48. #logfile stdout
  49. logfile /var/log/redis/redis.log
  51. # To enable logging to the system logger, just set 'syslog-enabled' to yes,
  52. # and optionally update the other syslog parameters to suit your needs.
  53. # syslog-enabled no
  55. # Specify the syslog identity.
  56. # syslog-ident redis
  58. # Specify the syslog facility.  Must be USER or between LOCAL0-LOCAL7.
  59. # syslog-facility local0
  61. # 可用数据库数
  62. # 默认值为16，默认数据库为0，数据库范围在0-（database-1）之间
  63. databases 16
  65. ################################ 快照  #################################
  66. #
  67. # 保存数据到磁盘，格式如下:
  68. #
  69. #   save <seconds> <changes>
  70. #
  71. #   指出在多长时间内，有多少次更新操作，就将数据同步到数据文件rdb。
  72. #   相当于条件触发抓取快照，这个可以多个条件配合
  73. #   
  74. #   比如默认配置文件中的设置，就设置了三个条件
  75. #
  76. #   save 900 1  900秒内至少有1个key被改变
  77. #   save 300 10  300秒内至少有300个key被改变
  78. #   save 60 10000  60秒内至少有10000个key被改变
  80. save 900 1
  81. save 300 10
  82. save 60 10000
  84. # 存储至本地数据库时（持久化到rdb文件）是否压缩数据，默认为yes
  85. rdbcompression yes
  88. # 本地持久化数据库文件名，默认值为dump.rdb
  89. dbfilename dump.rdb
  91. # 工作目录
  92. #
  93. # 数据库镜像备份的文件放置的路径。
  94. # 这里的路径跟文件名要分开配置是因为redis在进行备份时，先会将当前数据库的状态写入到一个临时文件中，等备份完成时，
  95. # 再把该该临时文件替换为上面所指定的文件，而这里的临时文件和上面所配置的备份文件都会放在这个指定的路径当中。
  96. #
  97. # AOF文件也会存放在这个目录下面
  98. #
  99. # 注意这里必须制定一个目录而不是文件
  100. dir ./
  102. ################################# 复制 #################################
  104. # 主从复制. 设置该数据库为其他数据库的从数据库.
  105. # 设置当本机为slav服务时，设置master服务的IP地址及端口，在Redis启动时，它会自动从master进行数据同步
  106. #
  107. # slaveof <masterip> <masterport>
  109. # 当master服务设置了密码保护时(用requirepass制定的密码)
  110. # slav服务连接master的密码
  111. #
  112. # masterauth <master-password>
  115. # 当从库同主机失去连接或者复制正在进行，从机库有两种运行方式：
  116. #
  117. # 1) 如果slave-serve-stale-data设置为yes(默认设置)，从库会继续相应客户端的请求
  118. #
  119. # 2) 如果slave-serve-stale-data是指为no，出去INFO和SLAVOF命令之外的任何请求都会返回一个
  120. #    错误"SYNC with master in progress"
  121. #
  122. slave-serve-stale-data yes
  124. # 从库会按照一个时间间隔向主库发送PINGs.可以通过repl-ping-slave-period设置这个时间间隔，默认是10秒
  125. #
  126. # repl-ping-slave-period 10
  128. # repl-timeout 设置主库批量数据传输时间或者ping回复时间间隔，默认值是60秒
  129. # 一定要确保repl-timeout大于repl-ping-slave-period
  130. # repl-timeout 60
  132. ################################## 安全 ###################################
  134. # 设置客户端连接后进行任何其他指定前需要使用的密码。
  135. # 警告：因为redis速度相当快，所以在一台比较好的服务器下，一个外部的用户可以在一秒钟进行150K次的密码尝试，这意味着你需要指定非常非常强大的密码来防止暴力破解
  136. #
  137. # requirepass foobared
  139. # 命令重命名.
  140. #
  141. # 在一个共享环境下可以重命名相对危险的命令。比如把CONFIG重名为一个不容易猜测的字符。
  142. #
  143. # 举例:
  144. #
  145. # rename-command CONFIG b840fc02d524045429941cc15f59e41cb7be6c52
  146. #
  147. # 如果想删除一个命令，直接把它重命名为一个空字符""即可，如下：
  148. #
  149. # rename-command CONFIG ""
  151. ################################### 约束 ####################################
  153. # 设置同一时间最大客户端连接数，默认无限制，Redis可以同时打开的客户端连接数为Redis进程可以打开的最大文件描述符数，
  154. # 如果设置 maxclients 0，表示不作限制。
  155. # 当客户端连接数到达限制时，Redis会关闭新的连接并向客户端返回max number of clients reached错误信息
  156. #
  157. # maxclients 128
  159. # 指定Redis最大内存限制，Redis在启动时会把数据加载到内存中，达到最大内存后，Redis会先尝试清除已到期或即将到期的Key
  160. # Redis同时也会移除空的list对象
  161. #
  162. # 当此方法处理后，仍然到达最大内存设置，将无法再进行写入操作，但仍然可以进行读取操作
  163. #
  164. # 注意：Redis新的vm机制，会把Key存放内存，Value会存放在swap区
  165. #
  166. # maxmemory的设置比较适合于把redis当作于类似memcached的缓存来使用，而不适合当做一个真实的DB。
  167. # 当把Redis当做一个真实的数据库使用的时候，内存使用将是一个很大的开销
  168. # maxmemory <bytes>
  170. # 当内存达到最大值的时候Redis会选择删除哪些数据？有五种方式可供选择
  171. #
  172. # volatile-lru -> 利用LRU算法移除设置过过期时间的key (LRU:最近使用 Least Recently Used )
  173. # allkeys-lru -> 利用LRU算法移除任何key
  174. # volatile-random -> 移除设置过过期时间的随机key
  175. # allkeys->random -> remove a random key, any key
  176. # volatile-ttl -> 移除即将过期的key(minor TTL)
  177. # noeviction -> 不移除任何可以，只是返回一个写错误
  178. #
  179. # 注意：对于上面的策略，如果没有合适的key可以移除，当写的时候Redis会返回一个错误
  180. #
  181. #       写命令包括: set setnx setex append
  182. #       incr decr rpush lpush rpushx lpushx linsert lset rpoplpush sadd
  183. #       sinter sinterstore sunion sunionstore sdiff sdiffstore zadd zincrby
  184. #       zunionstore zinterstore hset hsetnx hmset hincrby incrby decrby
  185. #       getset mset msetnx exec sort
  186. #
  187. # 默认是:
  188. #
  189. # maxmemory-policy volatile-lru
  191. # LRU 和 minimal TTL 算法都不是精准的算法，但是相对精确的算法(为了节省内存)，随意你可以选择样本大小进行检测。
  192. # Redis默认的灰选择3个样本进行检测，你可以通过maxmemory-samples进行设置
  193. #
  194. # maxmemory-samples 3
  196. ############################## AOF ###############################
  198. # 默认情况下，redis会在后台异步的把数据库镜像备份到磁盘，但是该备份是非常耗时的，而且备份也不能很频繁，如果发生诸如拉闸限电、拔插头等状况，那么将造成比较大范围的数据丢失。
  199. # 所以redis提供了另外一种更加高效的数据库备份及灾难恢复方式。
  200. # 开启append only模式之后，redis会把所接收到的每一次写操作请求都追加到appendonly.aof文件中，当redis重新启动时，会从该文件恢复出之前的状态。
  201. # 但是这样会造成appendonly.aof文件过大，所以redis还支持了BGREWRITEAOF指令，对appendonly.aof 进行重新整理。
  202. # 你可以同时开启asynchronous dumps 和 AOF
  204. appendonly no
  206. # AOF文件名称 (默认: "appendonly.aof")
  207. # appendfilename appendonly.aof
  210. # Redis支持三种同步AOF文件的策略:
  211. #
  212. # no: 不进行同步，系统去操作 . Faster.
  213. # always: always表示每次有写操作都进行同步. Slow, Safest.
  214. # everysec: 表示对写操作进行累积，每秒同步一次. Compromise.
  215. #
  216. # 默认是"everysec"，按照速度和安全折中这是最好的。
  217. # 如果想让Redis能更高效的运行，你也可以设置为"no"，让操作系统决定什么时候去执行
  218. # 或者相反想让数据更安全你也可以设置为"always"
  219. #
  220. # 如果不确定就用 "everysec".
  222. # appendfsync always
  223. appendfsync everysec
  224. # appendfsync no
  226. # AOF策略设置为always或者everysec时，后台处理进程(后台保存或者AOF日志重写)会执行大量的I/O操作
  227. # 在某些Linux配置中会阻止过长的fsync()请求。注意现在没有任何修复，即使fsync在另外一个线程进行处理
  228. #
  229. # 为了减缓这个问题，可以设置下面这个参数no-appendfsync-on-rewrite
  230. #
  231. # This means that while another child is saving the durability of Redis is
  232. # the same as "appendfsync none", that in pratical terms means that it is
  233. # possible to lost up to 30 seconds of log in the worst scenario (with the
  234. # default Linux settings).
  235. #
  236. # If you have latency problems turn this to "yes". Otherwise leave it as
  237. # "no" that is the safest pick from the point of view of durability.
  238. no-appendfsync-on-rewrite no
  240. # Automatic rewrite of the append only file.
  241. # AOF 自动重写
  242. # 当AOF文件增长到一定大小的时候Redis能够调用 BGREWRITEAOF 对日志文件进行重写
  243. #
  244. # 它是这样工作的：Redis会记住上次进行些日志后文件的大小(如果从开机以来还没进行过重写，那日子大小在开机的时候确定)
  245. #
  246. # 基础大小会同现在的大小进行比较。如果现在的大小比基础大小大制定的百分比，重写功能将启动
  247. # 同时需要指定一个最小大小用于AOF重写，这个用于阻止即使文件很小但是增长幅度很大也去重写AOF文件的情况
  248. # 设置 percentage 为0就关闭这个特性
  251. auto-aof-rewrite-percentage 100
  252. auto-aof-rewrite-min-size 64mb
  254. ################################## SLOW LOG ###################################
  256. # Redis Slow Log 记录超过特定执行时间的命令。执行时间不包括I/O计算比如连接客户端，返回结果等，只是命令执行时间
  257. #
  258. # 可以通过两个参数设置slow log：一个是告诉Redis执行超过多少时间被记录的参数slowlog-log-slower-than(微妙)，
  259. # 另一个是slow log 的长度。当一个新命令被记录的时候最早的命令将被从队列中移除
  262. # 下面的时间以微妙微单位，因此1000000代表一分钟。
  263. # 注意制定一个负数将关闭慢日志，而设置为0将强制每个命令都会记录
  264. slowlog-log-slower-than 10000
  267. # 对日志长度没有限制，只是要注意它会消耗内存
  268. # 可以通过 SLOWLOG RESET 回收被慢日志消耗的内存
  269. slowlog-max-len 1024
  271. ################################ VM ###############################
  273. ### WARNING! Virtual Memory is deprecated in Redis 2.4
  274. ### The use of Virtual Memory is strongly discouraged.
  276. # Virtual Memory allows Redis to work with datasets bigger than the actual
  277. # amount of RAM needed to hold the whole dataset in memory.
  278. # In order to do so very used keys are taken in memory while the other keys
  279. # are swapped into a swap file, similarly to what operating systems do
  280. # with memory pages.
  281. #
  282. # To enable VM just set 'vm-enabled' to yes, and set the following three
  283. # VM parameters accordingly to your needs.
  285. vm-enabled no
  286. # vm-enabled yes
  288. # This is the path of the Redis swap file. As you can guess, swap files
  289. # can't be shared by different Redis instances, so make sure to use a swap
  290. # file for every redis process you are running. Redis will complain if the
  291. # swap file is already in use.
  292. #
  293. # The best kind of storage for the Redis swap file (that's accessed at random)
  294. # is a Solid State Disk (SSD).
  295. #
  296. # *** WARNING *** if you are using a shared hosting the default of putting
  297. # the swap file under /tmp is not secure. Create a dir with access granted
  298. # only to Redis user and configure Redis to create the swap file there.
  299. vm-swap-file /tmp/redis.swap
  301. # vm-max-memory configures the VM to use at max the specified amount of
  302. # RAM. Everything that deos not fit will be swapped on disk *if* possible, that
  303. # is, if there is still enough contiguous space in the swap file.
  304. #
  305. # With vm-max-memory 0 the system will swap everything it can. Not a good
  306. # default, just specify the max amount of RAM you can in bytes, but it's
  307. # better to leave some margin. For instance specify an amount of RAM
  308. # that's more or less between 60 and 80% of your free RAM.
  309. vm-max-memory 0
  311. # Redis swap files is split into pages. An object can be saved using multiple
  312. # contiguous pages, but pages can't be shared between different objects.
  313. # So if your page is too big, small objects swapped out on disk will waste
  314. # a lot of space. If you page is too small, there is less space in the swap
  315. # file (assuming you configured the same number of total swap file pages).
  316. #
  317. # If you use a lot of small objects, use a page size of 64 or 32 bytes.
  318. # If you use a lot of big objects, use a bigger page size.
  319. # If unsure, use the default :)
  320. vm-page-size 32
  322. # Number of total memory pages in the swap file.
  323. # Given that the page table (a bitmap of free/used pages) is taken in memory,
  324. # every 8 pages on disk will consume 1 byte of RAM.
  325. #
  326. # The total swap size is vm-page-size * vm-pages
  327. #
  328. # With the default of 32-bytes memory pages and 134217728 pages Redis will
  329. # use a 4 GB swap file, that will use 16 MB of RAM for the page table.
  330. #
  331. # It's better to use the smallest acceptable value for your application,
  332. # but the default is large in order to work in most conditions.
  333. vm-pages 134217728
  335. # Max number of VM I/O threads running at the same time.
  336. # This threads are used to read/write data from/to swap file, since they
  337. # also encode and decode objects from disk to memory or the reverse, a bigger
  338. # number of threads can help with big objects even if they can't help with
  339. # I/O itself as the physical device may not be able to couple with many
  340. # reads/writes operations at the same time.
  341. #
  342. # The special value of 0 turn off threaded I/O and enables the blocking
  343. # Virtual Memory implementation.
  344. vm-max-threads 4
  346. ############################### ADVANCED CONFIG ###############################
  348. # 当hash中包含超过指定元素个数并且最大的元素没有超过临界时，
  349. # hash将以一种特殊的编码方式（大大减少内存使用）来存储，这里可以设置这两个临界值
  350. # Redis Hash对应Value内部实际就是一个HashMap，实际这里会有2种不同实现，
  351. # 这个Hash的成员比较少时Redis为了节省内存会采用类似一维数组的方式来紧凑存储，而不会采用真正的HashMap结构，对应的value redisObject的encoding为zipmap,
  352. # 当成员数量增大时会自动转成真正的HashMap,此时encoding为ht。
  353. hash-max-zipmap-entries 512
  354. hash-max-zipmap-value 64
  356. # list数据类型多少节点以下会采用去指针的紧凑存储格式。
  357. # list数据类型节点值大小小于多少字节会采用紧凑存储格式。
  358. list-max-ziplist-entries 512
  359. list-max-ziplist-value 64
  361. # set数据类型内部数据如果全部是数值型，且包含多少节点以下会采用紧凑格式存储。
  362. set-max-intset-entries 512
  364. # zsort数据类型多少节点以下会采用去指针的紧凑存储格式。
  365. # zsort数据类型节点值大小小于多少字节会采用紧凑存储格式。
  366. zset-max-ziplist-entries 128
  367. zset-max-ziplist-value 64
  370. # Redis将在每100毫秒时使用1毫秒的CPU时间来对redis的hash表进行重新hash，可以降低内存的使用
  371. #
  372. # 当你的使用场景中，有非常严格的实时性需要，不能够接受Redis时不时的对请求有2毫秒的延迟的话，把这项配置为no。
  373. #
  374. # 如果没有这么严格的实时性要求，可以设置为yes，以便能够尽可能快的释放内存
  375. activerehashing yes
  377. ################################## INCLUDES ###################################
  379. # 指定包含其它的配置文件，可以在同一主机上多个Redis实例之间使用同一份配置文件，而同时各个实例又拥有自己的特定配置文件
  381. # include /path/to/local.conf
  382. # include /path/to/other.conf

Version 5.08

  1. # Redis configuration file example.
  2. #
  3. # Note that in order to read the configuration file, Redis must be
  4. # started with the file path as first argument:
  5. #
  6. # ./redis-server /path/to/redis.conf
  8. # Note on units: when memory size is needed, it is possible to specify
  9. # it in the usual form of 1k 5GB 4M and so forth:
  10. #
  11. # 1k => 1000 bytes
  12. # 1kb => 1024 bytes
  13. # 1m => 1000000 bytes
  14. # 1mb => 1024*1024 bytes
  15. # 1g => 1000000000 bytes
  16. # 1gb => 1024*1024*1024 bytes
  17. #
  18. # units are case insensitive so 1GB 1Gb 1gB are all the same.
  20. ################################## INCLUDES ###################################
  22. # Include one or more other config files here.  This is useful if you
  23. # have a standard template that goes to all Redis servers but also need
  24. # to customize a few per-server settings.  Include files can include
  25. # other files, so use this wisely.
  26. #
  27. # Notice option "include" won't be rewritten by command "CONFIG REWRITE"
  28. # from admin or Redis Sentinel. Since Redis always uses the last processed
  29. # line as value of a configuration directive, you'd better put includes
  30. # at the beginning of this file to avoid overwriting config change at runtime.
  31. #
  32. # If instead you are interested in using includes to override configuration
  33. # options, it is better to use include as the last line.
  34. #
  35. # include /path/to/local.conf
  36. # include /path/to/other.conf
  38. ################################## MODULES #####################################
  40. # Load modules at startup. If the server is not able to load modules
  41. # it will abort. It is possible to use multiple loadmodule directives.
  42. #
  43. # loadmodule /path/to/my_module.so
  44. # loadmodule /path/to/other_module.so
  46. ################################## NETWORK #####################################
  48. # By default, if no "bind" configuration directive is specified, Redis listens
  49. # for connections from all the network interfaces available on the server.
  50. # It is possible to listen to just one or multiple selected interfaces using
  51. # the "bind" configuration directive, followed by one or more IP addresses.
  52. #
  53. # Examples:
  54. #
  55. # bind 192.168.1.100 10.0.0.1
  56. # bind 127.0.0.1 ::1
  57. #
  58. # ~~~ WARNING ~~~ If the computer running Redis is directly exposed to the
  59. # internet, binding to all the interfaces is dangerous and will expose the
  60. # instance to everybody on the internet. So by default we uncomment the
  61. # following bind directive, that will force Redis to listen only into
  62. # the IPv4 loopback interface address (this means Redis will be able to
  63. # accept connections only from clients running into the same computer it
  64. # is running).
  65. #
  66. # IF YOU ARE SURE YOU WANT YOUR INSTANCE TO LISTEN TO ALL THE INTERFACES
  67. # JUST COMMENT THE FOLLOWING LINE.
  68. # ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  69. bind 127.0.0.1
  71. # Protected mode is a layer of security protection, in order to avoid that
  72. # Redis instances left open on the internet are accessed and exploited.
  73. #
  74. # When protected mode is on and if:
  75. #
  76. # 1) The server is not binding explicitly to a set of addresses using the
  77. #    "bind" directive.
  78. # 2) No password is configured.
  79. #
  80. # The server only accepts connections from clients connecting from the
  81. # IPv4 and IPv6 loopback addresses 127.0.0.1 and ::1, and from Unix domain
  82. # sockets.
  83. #
  84. # By default protected mode is enabled. You should disable it only if
  85. # you are sure you want clients from other hosts to connect to Redis
  86. # even if no authentication is configured, nor a specific set of interfaces
  87. # are explicitly listed using the "bind" directive.
  88. protected-mode yes
  90. # Accept connections on the specified port, default is 6379 (IANA #815344).
  91. # If port 0 is specified Redis will not listen on a TCP socket.
  92. port 6379
  94. # TCP listen() backlog.
  95. #
  96. # In high requests-per-second environments you need an high backlog in order
  97. # to avoid slow clients connections issues. Note that the Linux kernel
  98. # will silently truncate it to the value of /proc/sys/net/core/somaxconn so
  99. # make sure to raise both the value of somaxconn and tcp_max_syn_backlog
  100. # in order to get the desired effect.
  101. tcp-backlog 511
  103. # Unix socket.
  104. #
  105. # Specify the path for the Unix socket that will be used to listen for
  106. # incoming connections. There is no default, so Redis will not listen
  107. # on a unix socket when not specified.
  108. #
  109. # unixsocket /tmp/redis.sock
  110. # unixsocketperm 700
  112. # Close the connection after a client is idle for N seconds (0 to disable)
  113. timeout 0
  115. # TCP keepalive.
  116. #
  117. # If non-zero, use SO_KEEPALIVE to send TCP ACKs to clients in absence
  118. # of communication. This is useful for two reasons:
  119. #
  120. # 1) Detect dead peers.
  121. # 2) Take the connection alive from the point of view of network
  122. #    equipment in the middle.
  123. #
  124. # On Linux, the specified value (in seconds) is the period used to send ACKs.
  125. # Note that to close the connection the double of the time is needed.
  126. # On other kernels the period depends on the kernel configuration.
  127. #
  128. # A reasonable value for this option is 300 seconds, which is the new
  129. # Redis default starting with Redis 3.2.1.
  130. tcp-keepalive 300
  132. ################################# GENERAL #####################################
  134. # By default Redis does not run as a daemon. Use 'yes' if you need it.
  135. # Note that Redis will write a pid file in /var/run/redis.pid when daemonized.
  136. daemonize no
  138. # If you run Redis from upstart or systemd, Redis can interact with your
  139. # supervision tree. Options:
  140. #   supervised no      - no supervision interaction
  141. #   supervised upstart - signal upstart by putting Redis into SIGSTOP mode
  142. #   supervised systemd - signal systemd by writing READY=1 to $NOTIFY_SOCKET
  143. #   supervised auto    - detect upstart or systemd method based on
  144. #                        UPSTART_JOB or NOTIFY_SOCKET environment variables
  145. # Note: these supervision methods only signal "process is ready."
  146. #       They do not enable continuous liveness pings back to your supervisor.
  147. supervised no
  149. # If a pid file is specified, Redis writes it where specified at startup
  150. # and removes it at exit.
  151. #
  152. # When the server runs non daemonized, no pid file is created if none is
  153. # specified in the configuration. When the server is daemonized, the pid file
  154. # is used even if not specified, defaulting to "/var/run/redis.pid".
  155. #
  156. # Creating a pid file is best effort: if Redis is not able to create it
  157. # nothing bad happens, the server will start and run normally.
  158. pidfile /var/run/redis_6379.pid
  160. # Specify the server verbosity level.
  161. # This can be one of:
  162. # debug (a lot of information, useful for development/testing)
  163. # verbose (many rarely useful info, but not a mess like the debug level)
  164. # notice (moderately verbose, what you want in production probably)
  165. # warning (only very important / critical messages are logged)
  166. loglevel notice
  168. # Specify the log file name. Also the empty string can be used to force
  169. # Redis to log on the standard output. Note that if you use standard
  170. # output for logging but daemonize, logs will be sent to /dev/null
  171. logfile ""
  173. # To enable logging to the system logger, just set 'syslog-enabled' to yes,
  174. # and optionally update the other syslog parameters to suit your needs.
  175. # syslog-enabled no
  177. # Specify the syslog identity.
  178. # syslog-ident redis
  180. # Specify the syslog facility. Must be USER or between LOCAL0-LOCAL7.
  181. # syslog-facility local0
  183. # Set the number of databases. The default database is DB 0, you can select
  184. # a different one on a per-connection basis using SELECT <dbid> where
  185. # dbid is a number between 0 and 'databases'-1
  186. databases 16
  188. # By default Redis shows an ASCII art logo only when started to log to the
  189. # standard output and if the standard output is a TTY. Basically this means
  190. # that normally a logo is displayed only in interactive sessions.
  191. #
  192. # However it is possible to force the pre-4.0 behavior and always show a
  193. # ASCII art logo in startup logs by setting the following option to yes.
  194. always-show-logo yes
  196. ################################ SNAPSHOTTING  ################################
  197. #
  198. # Save the DB on disk:
  199. #
  200. #   save <seconds> <changes>
  201. #
  202. #   Will save the DB if both the given number of seconds and the given
  203. #   number of write operations against the DB occurred.
  204. #
  205. #   In the example below the behaviour will be to save:
  206. #   after 900 sec (15 min) if at least 1 key changed
  207. #   after 300 sec (5 min) if at least 10 keys changed
  208. #   after 60 sec if at least 10000 keys changed
  209. #
  210. #   Note: you can disable saving completely by commenting out all "save" lines.
  211. #
  212. #   It is also possible to remove all the previously configured save
  213. #   points by adding a save directive with a single empty string argument
  214. #   like in the following example:
  215. #
  216. #   save ""
  218. save 900 1
  219. save 300 10
  220. save 60 10000
  222. # By default Redis will stop accepting writes if RDB snapshots are enabled
  223. # (at least one save point) and the latest background save failed.
  224. # This will make the user aware (in a hard way) that data is not persisting
  225. # on disk properly, otherwise chances are that no one will notice and some
  226. # disaster will happen.
  227. #
  228. # If the background saving process will start working again Redis will
  229. # automatically allow writes again.
  230. #
  231. # However if you have setup your proper monitoring of the Redis server
  232. # and persistence, you may want to disable this feature so that Redis will
  233. # continue to work as usual even if there are problems with disk,
  234. # permissions, and so forth.
  235. stop-writes-on-bgsave-error yes
  237. # Compress string objects using LZF when dump .rdb databases?
  238. # For default that's set to 'yes' as it's almost always a win.
  239. # If you want to save some CPU in the saving child set it to 'no' but
  240. # the dataset will likely be bigger if you have compressible values or keys.
  241. rdbcompression yes
  243. # Since version 5 of RDB a CRC64 checksum is placed at the end of the file.
  244. # This makes the format more resistant to corruption but there is a performance
  245. # hit to pay (around 10%) when saving and loading RDB files, so you can disable it
  246. # for maximum performances.
  247. #
  248. # RDB files created with checksum disabled have a checksum of zero that will
  249. # tell the loading code to skip the check.
  250. rdbchecksum yes
  252. # The filename where to dump the DB
  253. dbfilename dump.rdb
  255. # The working directory.
  256. #
  257. # The DB will be written inside this directory, with the filename specified
  258. # above using the 'dbfilename' configuration directive.
  259. #
  260. # The Append Only File will also be created inside this directory.
  261. #
  262. # Note that you must specify a directory here, not a file name.
  263. dir ./
  265. ################################# REPLICATION #################################
  267. # Master-Replica replication. Use replicaof to make a Redis instance a copy of
  268. # another Redis server. A few things to understand ASAP about Redis replication.
  269. #
  270. #   +------------------+      +---------------+
  271. #   |      Master      | ---> |    Replica    |
  272. #   | (receive writes) |      |  (exact copy) |
  273. #   +------------------+      +---------------+
  274. #
  275. # 1) Redis replication is asynchronous, but you can configure a master to
  276. #    stop accepting writes if it appears to be not connected with at least
  277. #    a given number of replicas.
  278. # 2) Redis replicas are able to perform a partial resynchronization with the
  279. #    master if the replication link is lost for a relatively small amount of
  280. #    time. You may want to configure the replication backlog size (see the next
  281. #    sections of this file) with a sensible value depending on your needs.
  282. # 3) Replication is automatic and does not need user intervention. After a
  283. #    network partition replicas automatically try to reconnect to masters
  284. #    and resynchronize with them.
  285. #
  286. # replicaof <masterip> <masterport>
  288. # If the master is password protected (using the "requirepass" configuration
  289. # directive below) it is possible to tell the replica to authenticate before
  290. # starting the replication synchronization process, otherwise the master will
  291. # refuse the replica request.
  292. #
  293. # masterauth <master-password>
  295. # When a replica loses its connection with the master, or when the replication
  296. # is still in progress, the replica can act in two different ways:
  297. #
  298. # 1) if replica-serve-stale-data is set to 'yes' (the default) the replica will
  299. #    still reply to client requests, possibly with out of date data, or the
  300. #    data set may just be empty if this is the first synchronization.
  301. #
  302. # 2) if replica-serve-stale-data is set to 'no' the replica will reply with
  303. #    an error "SYNC with master in progress" to all the kind of commands
  304. #    but to INFO, replicaOF, AUTH, PING, SHUTDOWN, REPLCONF, ROLE, CONFIG,
  305. #    SUBSCRIBE, UNSUBSCRIBE, PSUBSCRIBE, PUNSUBSCRIBE, PUBLISH, PUBSUB,
  306. #    COMMAND, POST, HOST: and LATENCY.
  307. #
  308. replica-serve-stale-data yes
  310. # You can configure a replica instance to accept writes or not. Writing against
  311. # a replica instance may be useful to store some ephemeral data (because data
  312. # written on a replica will be easily deleted after resync with the master) but
  313. # may also cause problems if clients are writing to it because of a
  314. # misconfiguration.
  315. #
  316. # Since Redis 2.6 by default replicas are read-only.
  317. #
  318. # Note: read only replicas are not designed to be exposed to untrusted clients
  319. # on the internet. It's just a protection layer against misuse of the instance.
  320. # Still a read only replica exports by default all the administrative commands
  321. # such as CONFIG, DEBUG, and so forth. To a limited extent you can improve
  322. # security of read only replicas using 'rename-command' to shadow all the
  323. # administrative / dangerous commands.
  324. replica-read-only yes
  326. # Replication SYNC strategy: disk or socket.
  327. #
  328. # -------------------------------------------------------
  329. # WARNING: DISKLESS REPLICATION IS EXPERIMENTAL CURRENTLY
  330. # -------------------------------------------------------
  331. #
  332. # New replicas and reconnecting replicas that are not able to continue the replication
  333. # process just receiving differences, need to do what is called a "full
  334. # synchronization". An RDB file is transmitted from the master to the replicas.
  335. # The transmission can happen in two different ways:
  336. #
  337. # 1) Disk-backed: The Redis master creates a new process that writes the RDB
  338. #                 file on disk. Later the file is transferred by the parent
  339. #                 process to the replicas incrementally.
  340. # 2) Diskless: The Redis master creates a new process that directly writes the
  341. #              RDB file to replica sockets, without touching the disk at all.
  342. #
  343. # With disk-backed replication, while the RDB file is generated, more replicas
  344. # can be queued and served with the RDB file as soon as the current child producing
  345. # the RDB file finishes its work. With diskless replication instead once
  346. # the transfer starts, new replicas arriving will be queued and a new transfer
  347. # will start when the current one terminates.
  348. #
  349. # When diskless replication is used, the master waits a configurable amount of
  350. # time (in seconds) before starting the transfer in the hope that multiple replicas
  351. # will arrive and the transfer can be parallelized.
  352. #
  353. # With slow disks and fast (large bandwidth) networks, diskless replication
  354. # works better.
  355. repl-diskless-sync no
  357. # When diskless replication is enabled, it is possible to configure the delay
  358. # the server waits in order to spawn the child that transfers the RDB via socket
  359. # to the replicas.
  360. #
  361. # This is important since once the transfer starts, it is not possible to serve
  362. # new replicas arriving, that will be queued for the next RDB transfer, so the server
  363. # waits a delay in order to let more replicas arrive.
  364. #
  365. # The delay is specified in seconds, and by default is 5 seconds. To disable
  366. # it entirely just set it to 0 seconds and the transfer will start ASAP.
  367. repl-diskless-sync-delay 5
  369. # Replicas send PINGs to server in a predefined interval. It's possible to change
  370. # this interval with the repl_ping_replica_period option. The default value is 10
  371. # seconds.
  372. #
  373. # repl-ping-replica-period 10
  375. # The following option sets the replication timeout for:
  376. #
  377. # 1) Bulk transfer I/O during SYNC, from the point of view of replica.
  378. # 2) Master timeout from the point of view of replicas (data, pings).
  379. # 3) Replica timeout from the point of view of masters (REPLCONF ACK pings).
  380. #
  381. # It is important to make sure that this value is greater than the value
  382. # specified for repl-ping-replica-period otherwise a timeout will be detected
  383. # every time there is low traffic between the master and the replica.
  384. #
  385. # repl-timeout 60
  387. # Disable TCP_NODELAY on the replica socket after SYNC?
  388. #
  389. # If you select "yes" Redis will use a smaller number of TCP packets and
  390. # less bandwidth to send data to replicas. But this can add a delay for
  391. # the data to appear on the replica side, up to 40 milliseconds with
  392. # Linux kernels using a default configuration.
  393. #
  394. # If you select "no" the delay for data to appear on the replica side will
  395. # be reduced but more bandwidth will be used for replication.
  396. #
  397. # By default we optimize for low latency, but in very high traffic conditions
  398. # or when the master and replicas are many hops away, turning this to "yes" may
  399. # be a good idea.
  400. repl-disable-tcp-nodelay no
  402. # Set the replication backlog size. The backlog is a buffer that accumulates
  403. # replica data when replicas are disconnected for some time, so that when a replica
  404. # wants to reconnect again, often a full resync is not needed, but a partial
  405. # resync is enough, just passing the portion of data the replica missed while
  406. # disconnected.
  407. #
  408. # The bigger the replication backlog, the longer the time the replica can be
  409. # disconnected and later be able to perform a partial resynchronization.
  410. #
  411. # The backlog is only allocated once there is at least a replica connected.
  412. #
  413. # repl-backlog-size 1mb
  415. # After a master has no longer connected replicas for some time, the backlog
  416. # will be freed. The following option configures the amount of seconds that
  417. # need to elapse, starting from the time the last replica disconnected, for
  418. # the backlog buffer to be freed.
  419. #
  420. # Note that replicas never free the backlog for timeout, since they may be
  421. # promoted to masters later, and should be able to correctly "partially
  422. # resynchronize" with the replicas: hence they should always accumulate backlog.
  423. #
  424. # A value of 0 means to never release the backlog.
  425. #
  426. # repl-backlog-ttl 3600
  428. # The replica priority is an integer number published by Redis in the INFO output.
  429. # It is used by Redis Sentinel in order to select a replica to promote into a
  430. # master if the master is no longer working correctly.
  431. #
  432. # A replica with a low priority number is considered better for promotion, so
  433. # for instance if there are three replicas with priority 10, 100, 25 Sentinel will
  434. # pick the one with priority 10, that is the lowest.
  435. #
  436. # However a special priority of 0 marks the replica as not able to perform the
  437. # role of master, so a replica with priority of 0 will never be selected by
  438. # Redis Sentinel for promotion.
  439. #
  440. # By default the priority is 100.
  441. replica-priority 100
  443. # It is possible for a master to stop accepting writes if there are less than
  444. # N replicas connected, having a lag less or equal than M seconds.
  445. #
  446. # The N replicas need to be in "online" state.
  447. #
  448. # The lag in seconds, that must be <= the specified value, is calculated from
  449. # the last ping received from the replica, that is usually sent every second.
  450. #
  451. # This option does not GUARANTEE that N replicas will accept the write, but
  452. # will limit the window of exposure for lost writes in case not enough replicas
  453. # are available, to the specified number of seconds.
  454. #
  455. # For example to require at least 3 replicas with a lag <= 10 seconds use:
  456. #
  457. # min-replicas-to-write 3
  458. # min-replicas-max-lag 10
  459. #
  460. # Setting one or the other to 0 disables the feature.
  461. #
  462. # By default min-replicas-to-write is set to 0 (feature disabled) and
  463. # min-replicas-max-lag is set to 10.
  465. # A Redis master is able to list the address and port of the attached
  466. # replicas in different ways. For example the "INFO replication" section
  467. # offers this information, which is used, among other tools, by
  468. # Redis Sentinel in order to discover replica instances.
  469. # Another place where this info is available is in the output of the
  470. # "ROLE" command of a master.
  471. #
  472. # The listed IP and address normally reported by a replica is obtained
  473. # in the following way:
  474. #
  475. #   IP: The address is auto detected by checking the peer address
  476. #   of the socket used by the replica to connect with the master.
  477. #
  478. #   Port: The port is communicated by the replica during the replication
  479. #   handshake, and is normally the port that the replica is using to
  480. #   listen for connections.
  481. #
  482. # However when port forwarding or Network Address Translation (NAT) is
  483. # used, the replica may be actually reachable via different IP and port
  484. # pairs. The following two options can be used by a replica in order to
  485. # report to its master a specific set of IP and port, so that both INFO
  486. # and ROLE will report those values.
  487. #
  488. # There is no need to use both the options if you need to override just
  489. # the port or the IP address.
  490. #
  491. # replica-announce-ip 5.5.5.5
  492. # replica-announce-port 1234
  494. ################################## SECURITY ###################################
  496. # Require clients to issue AUTH <PASSWORD> before processing any other
  497. # commands.  This might be useful in environments in which you do not trust
  498. # others with access to the host running redis-server.
  499. #
  500. # This should stay commented out for backward compatibility and because most
  501. # people do not need auth (e.g. they run their own servers).
  502. #
  503. # Warning: since Redis is pretty fast an outside user can try up to
  504. # 150k passwords per second against a good box. This means that you should
  505. # use a very strong password otherwise it will be very easy to break.
  506. #
  507. # requirepass foobared
  509. # Command renaming.
  510. #
  511. # It is possible to change the name of dangerous commands in a shared
  512. # environment. For instance the CONFIG command may be renamed into something
  513. # hard to guess so that it will still be available for internal-use tools
  514. # but not available for general clients.
  515. #
  516. # Example:
  517. #
  518. # rename-command CONFIG b840fc02d524045429941cc15f59e41cb7be6c52
  519. #
  520. # It is also possible to completely kill a command by renaming it into
  521. # an empty string:
  522. #
  523. # rename-command CONFIG ""
  524. #
  525. # Please note that changing the name of commands that are logged into the
  526. # AOF file or transmitted to replicas may cause problems.
  528. ################################### CLIENTS ####################################
  530. # Set the max number of connected clients at the same time. By default
  531. # this limit is set to 10000 clients, however if the Redis server is not
  532. # able to configure the process file limit to allow for the specified limit
  533. # the max number of allowed clients is set to the current file limit
  534. # minus 32 (as Redis reserves a few file descriptors for internal uses).
  535. #
  536. # Once the limit is reached Redis will close all the new connections sending
  537. # an error 'max number of clients reached'.
  538. #
  539. # maxclients 10000
  541. ############################## MEMORY MANAGEMENT ################################
  543. # Set a memory usage limit to the specified amount of bytes.
  544. # When the memory limit is reached Redis will try to remove keys
  545. # according to the eviction policy selected (see maxmemory-policy).
  546. #
  547. # If Redis can't remove keys according to the policy, or if the policy is
  548. # set to 'noeviction', Redis will start to reply with errors to commands
  549. # that would use more memory, like SET, LPUSH, and so on, and will continue
  550. # to reply to read-only commands like GET.
  551. #
  552. # This option is usually useful when using Redis as an LRU or LFU cache, or to
  553. # set a hard memory limit for an instance (using the 'noeviction' policy).
  554. #
  555. # WARNING: If you have replicas attached to an instance with maxmemory on,
  556. # the size of the output buffers needed to feed the replicas are subtracted
  557. # from the used memory count, so that network problems / resyncs will
  558. # not trigger a loop where keys are evicted, and in turn the output
  559. # buffer of replicas is full with DELs of keys evicted triggering the deletion
  560. # of more keys, and so forth until the database is completely emptied.
  561. #
  562. # In short... if you have replicas attached it is suggested that you set a lower
  563. # limit for maxmemory so that there is some free RAM on the system for replica
  564. # output buffers (but this is not needed if the policy is 'noeviction').
  565. #
  566. # maxmemory <bytes>
  568. # MAXMEMORY POLICY: how Redis will select what to remove when maxmemory
  569. # is reached. You can select among five behaviors:
  570. #
  571. # volatile-lru -> Evict using approximated LRU among the keys with an expire set.
  572. # allkeys-lru -> Evict any key using approximated LRU.
  573. # volatile-lfu -> Evict using approximated LFU among the keys with an expire set.
  574. # allkeys-lfu -> Evict any key using approximated LFU.
  575. # volatile-random -> Remove a random key among the ones with an expire set.
  576. # allkeys-random -> Remove a random key, any key.
  577. # volatile-ttl -> Remove the key with the nearest expire time (minor TTL)
  578. # noeviction -> Don't evict anything, just return an error on write operations.
  579. #
  580. # LRU means Least Recently Used
  581. # LFU means Least Frequently Used
  582. #
  583. # Both LRU, LFU and volatile-ttl are implemented using approximated
  584. # randomized algorithms.
  585. #
  586. # Note: with any of the above policies, Redis will return an error on write
  587. #       operations, when there are no suitable keys for eviction.
  588. #
  589. #       At the date of writing these commands are: set setnx setex append
  590. #       incr decr rpush lpush rpushx lpushx linsert lset rpoplpush sadd
  591. #       sinter sinterstore sunion sunionstore sdiff sdiffstore zadd zincrby
  592. #       zunionstore zinterstore hset hsetnx hmset hincrby incrby decrby
  593. #       getset mset msetnx exec sort
  594. #
  595. # The default is:
  596. #
  597. # maxmemory-policy noeviction
  599. # LRU, LFU and minimal TTL algorithms are not precise algorithms but approximated
  600. # algorithms (in order to save memory), so you can tune it for speed or
  601. # accuracy. For default Redis will check five keys and pick the one that was
  602. # used less recently, you can change the sample size using the following
  603. # configuration directive.
  604. #
  605. # The default of 5 produces good enough results. 10 Approximates very closely
  606. # true LRU but costs more CPU. 3 is faster but not very accurate.
  607. #
  608. # maxmemory-samples 5
  610. # Starting from Redis 5, by default a replica will ignore its maxmemory setting
  611. # (unless it is promoted to master after a failover or manually). It means
  612. # that the eviction of keys will be just handled by the master, sending the
  613. # DEL commands to the replica as keys evict in the master side.
  614. #
  615. # This behavior ensures that masters and replicas stay consistent, and is usually
  616. # what you want, however if your replica is writable, or you want the replica to have
  617. # a different memory setting, and you are sure all the writes performed to the
  618. # replica are idempotent, then you may change this default (but be sure to understand
  619. # what you are doing).
  620. #
  621. # Note that since the replica by default does not evict, it may end using more
  622. # memory than the one set via maxmemory (there are certain buffers that may
  623. # be larger on the replica, or data structures may sometimes take more memory and so
  624. # forth). So make sure you monitor your replicas and make sure they have enough
  625. # memory to never hit a real out-of-memory condition before the master hits
  626. # the configured maxmemory setting.
  627. #
  628. # replica-ignore-maxmemory yes
  630. ############################# LAZY FREEING ####################################
  632. # Redis has two primitives to delete keys. One is called DEL and is a blocking
  633. # deletion of the object. It means that the server stops processing new commands
  634. # in order to reclaim all the memory associated with an object in a synchronous
  635. # way. If the key deleted is associated with a small object, the time needed
  636. # in order to execute the DEL command is very small and comparable to most other
  637. # O(1) or O(log_N) commands in Redis. However if the key is associated with an
  638. # aggregated value containing millions of elements, the server can block for
  639. # a long time (even seconds) in order to complete the operation.
  640. #
  641. # For the above reasons Redis also offers non blocking deletion primitives
  642. # such as UNLINK (non blocking DEL) and the ASYNC option of FLUSHALL and
  643. # FLUSHDB commands, in order to reclaim memory in background. Those commands
  644. # are executed in constant time. Another thread will incrementally free the
  645. # object in the background as fast as possible.
  646. #
  647. # DEL, UNLINK and ASYNC option of FLUSHALL and FLUSHDB are user-controlled.
  648. # It's up to the design of the application to understand when it is a good
  649. # idea to use one or the other. However the Redis server sometimes has to
  650. # delete keys or flush the whole database as a side effect of other operations.
  651. # Specifically Redis deletes objects independently of a user call in the
  652. # following scenarios:
  653. #
  654. # 1) On eviction, because of the maxmemory and maxmemory policy configurations,
  655. #    in order to make room for new data, without going over the specified
  656. #    memory limit.
  657. # 2) Because of expire: when a key with an associated time to live (see the
  658. #    EXPIRE command) must be deleted from memory.
  659. # 3) Because of a side effect of a command that stores data on a key that may
  660. #    already exist. For example the RENAME command may delete the old key
  661. #    content when it is replaced with another one. Similarly SUNIONSTORE
  662. #    or SORT with STORE option may delete existing keys. The SET command
  663. #    itself removes any old content of the specified key in order to replace
  664. #    it with the specified string.
  665. # 4) During replication, when a replica performs a full resynchronization with
  666. #    its master, the content of the whole database is removed in order to
  667. #    load the RDB file just transferred.
  668. #
  669. # In all the above cases the default is to delete objects in a blocking way,
  670. # like if DEL was called. However you can configure each case specifically
  671. # in order to instead release memory in a non-blocking way like if UNLINK
  672. # was called, using the following configuration directives:
  674. lazyfree-lazy-eviction no
  675. lazyfree-lazy-expire no
  676. lazyfree-lazy-server-del no
  677. replica-lazy-flush no
  679. ############################## APPEND ONLY MODE ###############################
  681. # By default Redis asynchronously dumps the dataset on disk. This mode is
  682. # good enough in many applications, but an issue with the Redis process or
  683. # a power outage may result into a few minutes of writes lost (depending on
  684. # the configured save points).
  685. #
  686. # The Append Only File is an alternative persistence mode that provides
  687. # much better durability. For instance using the default data fsync policy
  688. # (see later in the config file) Redis can lose just one second of writes in a
  689. # dramatic event like a server power outage, or a single write if something
  690. # wrong with the Redis process itself happens, but the operating system is
  691. # still running correctly.
  692. #
  693. # AOF and RDB persistence can be enabled at the same time without problems.
  694. # If the AOF is enabled on startup Redis will load the AOF, that is the file
  695. # with the better durability guarantees.
  696. #
  697. # Please check http://redis.io/topics/persistence for more information.
  699. appendonly no
  701. # The name of the append only file (default: "appendonly.aof")
  703. appendfilename "appendonly.aof"
  705. # The fsync() call tells the Operating System to actually write data on disk
  706. # instead of waiting for more data in the output buffer. Some OS will really flush
  707. # data on disk, some other OS will just try to do it ASAP.
  708. #
  709. # Redis supports three different modes:
  710. #
  711. # no: don't fsync, just let the OS flush the data when it wants. Faster.
  712. # always: fsync after every write to the append only log. Slow, Safest.
  713. # everysec: fsync only one time every second. Compromise.
  714. #
  715. # The default is "everysec", as that's usually the right compromise between
  716. # speed and data safety. It's up to you to understand if you can relax this to
  717. # "no" that will let the operating system flush the output buffer when
  718. # it wants, for better performances (but if you can live with the idea of
  719. # some data loss consider the default persistence mode that's snapshotting),
  720. # or on the contrary, use "always" that's very slow but a bit safer than
  721. # everysec.
  722. #
  723. # More details please check the following article:
  724. # http://antirez.com/post/redis-persistence-demystified.html
  725. #
  726. # If unsure, use "everysec".
  728. # appendfsync always
  729. appendfsync everysec
  730. # appendfsync no
  732. # When the AOF fsync policy is set to always or everysec, and a background
  733. # saving process (a background save or AOF log background rewriting) is
  734. # performing a lot of I/O against the disk, in some Linux configurations
  735. # Redis may block too long on the fsync() call. Note that there is no fix for
  736. # this currently, as even performing fsync in a different thread will block
  737. # our synchronous write(2) call.
  738. #
  739. # In order to mitigate this problem it's possible to use the following option
  740. # that will prevent fsync() from being called in the main process while a
  741. # BGSAVE or BGREWRITEAOF is in progress.
  742. #
  743. # This means that while another child is saving, the durability of Redis is
  744. # the same as "appendfsync none". In practical terms, this means that it is
  745. # possible to lose up to 30 seconds of log in the worst scenario (with the
  746. # default Linux settings).
  747. #
  748. # If you have latency problems turn this to "yes". Otherwise leave it as
  749. # "no" that is the safest pick from the point of view of durability.
  751. no-appendfsync-on-rewrite no
  753. # Automatic rewrite of the append only file.
  754. # Redis is able to automatically rewrite the log file implicitly calling
  755. # BGREWRITEAOF when the AOF log size grows by the specified percentage.
  756. #
  757. # This is how it works: Redis remembers the size of the AOF file after the
  758. # latest rewrite (if no rewrite has happened since the restart, the size of
  759. # the AOF at startup is used).
  760. #
  761. # This base size is compared to the current size. If the current size is
  762. # bigger than the specified percentage, the rewrite is triggered. Also
  763. # you need to specify a minimal size for the AOF file to be rewritten, this
  764. # is useful to avoid rewriting the AOF file even if the percentage increase
  765. # is reached but it is still pretty small.
  766. #
  767. # Specify a percentage of zero in order to disable the automatic AOF
  768. # rewrite feature.
  770. auto-aof-rewrite-percentage 100
  771. auto-aof-rewrite-min-size 64mb
  773. # An AOF file may be found to be truncated at the end during the Redis
  774. # startup process, when the AOF data gets loaded back into memory.
  775. # This may happen when the system where Redis is running
  776. # crashes, especially when an ext4 filesystem is mounted without the
  777. # data=ordered option (however this can't happen when Redis itself
  778. # crashes or aborts but the operating system still works correctly).
  779. #
  780. # Redis can either exit with an error when this happens, or load as much
  781. # data as possible (the default now) and start if the AOF file is found
  782. # to be truncated at the end. The following option controls this behavior.
  783. #
  784. # If aof-load-truncated is set to yes, a truncated AOF file is loaded and
  785. # the Redis server starts emitting a log to inform the user of the event.
  786. # Otherwise if the option is set to no, the server aborts with an error
  787. # and refuses to start. When the option is set to no, the user requires
  788. # to fix the AOF file using the "redis-check-aof" utility before to restart
  789. # the server.
  790. #
  791. # Note that if the AOF file will be found to be corrupted in the middle
  792. # the server will still exit with an error. This option only applies when
  793. # Redis will try to read more data from the AOF file but not enough bytes
  794. # will be found.
  795. aof-load-truncated yes
  797. # When rewriting the AOF file, Redis is able to use an RDB preamble in the
  798. # AOF file for faster rewrites and recoveries. When this option is turned
  799. # on the rewritten AOF file is composed of two different stanzas:
  800. #
  801. #   [RDB file][AOF tail]
  802. #
  803. # When loading Redis recognizes that the AOF file starts with the "REDIS"
  804. # string and loads the prefixed RDB file, and continues loading the AOF
  805. # tail.
  806. aof-use-rdb-preamble yes
  808. ################################ LUA SCRIPTING  ###############################
  810. # Max execution time of a Lua script in milliseconds.
  811. #
  812. # If the maximum execution time is reached Redis will log that a script is
  813. # still in execution after the maximum allowed time and will start to
  814. # reply to queries with an error.
  815. #
  816. # When a long running script exceeds the maximum execution time only the
  817. # SCRIPT KILL and SHUTDOWN NOSAVE commands are available. The first can be
  818. # used to stop a script that did not yet called write commands. The second
  819. # is the only way to shut down the server in the case a write command was
  820. # already issued by the script but the user doesn't want to wait for the natural
  821. # termination of the script.
  822. #
  823. # Set it to 0 or a negative value for unlimited execution without warnings.
  824. lua-time-limit 5000
  826. ################################ REDIS CLUSTER  ###############################
  828. # Normal Redis instances can't be part of a Redis Cluster; only nodes that are
  829. # started as cluster nodes can. In order to start a Redis instance as a
  830. # cluster node enable the cluster support uncommenting the following:
  831. #
  832. # cluster-enabled yes
  834. # Every cluster node has a cluster configuration file. This file is not
  835. # intended to be edited by hand. It is created and updated by Redis nodes.
  836. # Every Redis Cluster node requires a different cluster configuration file.
  837. # Make sure that instances running in the same system do not have
  838. # overlapping cluster configuration file names.
  839. #
  840. # cluster-config-file nodes-6379.conf
  842. # Cluster node timeout is the amount of milliseconds a node must be unreachable
  843. # for it to be considered in failure state.
  844. # Most other internal time limits are multiple of the node timeout.
  845. #
  846. # cluster-node-timeout 15000
  848. # A replica of a failing master will avoid to start a failover if its data
  849. # looks too old.
  850. #
  851. # There is no simple way for a replica to actually have an exact measure of
  852. # its "data age", so the following two checks are performed:
  853. #
  854. # 1) If there are multiple replicas able to failover, they exchange messages
  855. #    in order to try to give an advantage to the replica with the best
  856. #    replication offset (more data from the master processed).
  857. #    Replicas will try to get their rank by offset, and apply to the start
  858. #    of the failover a delay proportional to their rank.
  859. #
  860. # 2) Every single replica computes the time of the last interaction with
  861. #    its master. This can be the last ping or command received (if the master
  862. #    is still in the "connected" state), or the time that elapsed since the
  863. #    disconnection with the master (if the replication link is currently down).
  864. #    If the last interaction is too old, the replica will not try to failover
  865. #    at all.
  866. #
  867. # The point "2" can be tuned by user. Specifically a replica will not perform
  868. # the failover if, since the last interaction with the master, the time
  869. # elapsed is greater than:
  870. #
  871. #   (node-timeout * replica-validity-factor) + repl-ping-replica-period
  872. #
  873. # So for example if node-timeout is 30 seconds, and the replica-validity-factor
  874. # is 10, and assuming a default repl-ping-replica-period of 10 seconds, the
  875. # replica will not try to failover if it was not able to talk with the master
  876. # for longer than 310 seconds.
  877. #
  878. # A large replica-validity-factor may allow replicas with too old data to failover
  879. # a master, while a too small value may prevent the cluster from being able to
  880. # elect a replica at all.
  881. #
  882. # For maximum availability, it is possible to set the replica-validity-factor
  883. # to a value of 0, which means, that replicas will always try to failover the
  884. # master regardless of the last time they interacted with the master.
  885. # (However they'll always try to apply a delay proportional to their
  886. # offset rank).
  887. #
  888. # Zero is the only value able to guarantee that when all the partitions heal
  889. # the cluster will always be able to continue.
  890. #
  891. # cluster-replica-validity-factor 10
  893. # Cluster replicas are able to migrate to orphaned masters, that are masters
  894. # that are left without working replicas. This improves the cluster ability
  895. # to resist to failures as otherwise an orphaned master can't be failed over
  896. # in case of failure if it has no working replicas.
  897. #
  898. # Replicas migrate to orphaned masters only if there are still at least a
  899. # given number of other working replicas for their old master. This number
  900. # is the "migration barrier". A migration barrier of 1 means that a replica
  901. # will migrate only if there is at least 1 other working replica for its master
  902. # and so forth. It usually reflects the number of replicas you want for every
  903. # master in your cluster.
  904. #
  905. # Default is 1 (replicas migrate only if their masters remain with at least
  906. # one replica). To disable migration just set it to a very large value.
  907. # A value of 0 can be set but is useful only for debugging and dangerous
  908. # in production.
  909. #
  910. # cluster-migration-barrier 1
  912. # By default Redis Cluster nodes stop accepting queries if they detect there
  913. # is at least an hash slot uncovered (no available node is serving it).
  914. # This way if the cluster is partially down (for example a range of hash slots
  915. # are no longer covered) all the cluster becomes, eventually, unavailable.
  916. # It automatically returns available as soon as all the slots are covered again.
  917. #
  918. # However sometimes you want the subset of the cluster which is working,
  919. # to continue to accept queries for the part of the key space that is still
  920. # covered. In order to do so, just set the cluster-require-full-coverage
  921. # option to no.
  922. #
  923. # cluster-require-full-coverage yes
  925. # This option, when set to yes, prevents replicas from trying to failover its
  926. # master during master failures. However the master can still perform a
  927. # manual failover, if forced to do so.
  928. #
  929. # This is useful in different scenarios, especially in the case of multiple
  930. # data center operations, where we want one side to never be promoted if not
  931. # in the case of a total DC failure.
  932. #
  933. # cluster-replica-no-failover no
  935. # In order to setup your cluster make sure to read the documentation
  936. # available at http://redis.io web site.
  938. ########################## CLUSTER DOCKER/NAT support  ########################
  940. # In certain deployments, Redis Cluster nodes address discovery fails, because
  941. # addresses are NAT-ted or because ports are forwarded (the typical case is
  942. # Docker and other containers).
  943. #
  944. # In order to make Redis Cluster working in such environments, a static
  945. # configuration where each node knows its public address is needed. The
  946. # following two options are used for this scope, and are:
  947. #
  948. # * cluster-announce-ip
  949. # * cluster-announce-port
  950. # * cluster-announce-bus-port
  951. #
  952. # Each instruct the node about its address, client port, and cluster message
  953. # bus port. The information is then published in the header of the bus packets
  954. # so that other nodes will be able to correctly map the address of the node
  955. # publishing the information.
  956. #
  957. # If the above options are not used, the normal Redis Cluster auto-detection
  958. # will be used instead.
  959. #
  960. # Note that when remapped, the bus port may not be at the fixed offset of
  961. # clients port + 10000, so you can specify any port and bus-port depending
  962. # on how they get remapped. If the bus-port is not set, a fixed offset of
  963. # 10000 will be used as usually.
  964. #
  965. # Example:
  966. #
  967. # cluster-announce-ip 10.1.1.5
  968. # cluster-announce-port 6379
  969. # cluster-announce-bus-port 6380
  971. ################################## SLOW LOG ###################################
  973. # The Redis Slow Log is a system to log queries that exceeded a specified
  974. # execution time. The execution time does not include the I/O operations
  975. # like talking with the client, sending the reply and so forth,
  976. # but just the time needed to actually execute the command (this is the only
  977. # stage of command execution where the thread is blocked and can not serve
  978. # other requests in the meantime).
  979. #
  980. # You can configure the slow log with two parameters: one tells Redis
  981. # what is the execution time, in microseconds, to exceed in order for the
  982. # command to get logged, and the other parameter is the length of the
  983. # slow log. When a new command is logged the oldest one is removed from the
  984. # queue of logged commands.
  986. # The following time is expressed in microseconds, so 1000000 is equivalent
  987. # to one second. Note that a negative number disables the slow log, while
  988. # a value of zero forces the logging of every command.
  989. slowlog-log-slower-than 10000
  991. # There is no limit to this length. Just be aware that it will consume memory.
  992. # You can reclaim memory used by the slow log with SLOWLOG RESET.
  993. slowlog-max-len 128
  995. ################################ LATENCY MONITOR ##############################
  997. # The Redis latency monitoring subsystem samples different operations
  998. # at runtime in order to collect data related to possible sources of
  999. # latency of a Redis instance.
  1000. #
  1001. # Via the LATENCY command this information is available to the user that can
  1002. # print graphs and obtain reports.
  1003. #
  1004. # The system only logs operations that were performed in a time equal or
  1005. # greater than the amount of milliseconds specified via the
  1006. # latency-monitor-threshold configuration directive. When its value is set
  1007. # to zero, the latency monitor is turned off.
  1008. #
  1009. # By default latency monitoring is disabled since it is mostly not needed
  1010. # if you don't have latency issues, and collecting data has a performance
  1011. # impact, that while very small, can be measured under big load. Latency
  1012. # monitoring can easily be enabled at runtime using the command
  1013. # "CONFIG SET latency-monitor-threshold <milliseconds>" if needed.
  1014. latency-monitor-threshold 0
  1016. ############################# EVENT NOTIFICATION ##############################
  1018. # Redis can notify Pub/Sub clients about events happening in the key space.
  1019. # This feature is documented at http://redis.io/topics/notifications
  1020. #
  1021. # For instance if keyspace events notification is enabled, and a client
  1022. # performs a DEL operation on key "foo" stored in the Database 0, two
  1023. # messages will be published via Pub/Sub:
  1024. #
  1025. # PUBLISH __keyspace@0__:foo del
  1026. # PUBLISH __keyevent@0__:del foo
  1027. #
  1028. # It is possible to select the events that Redis will notify among a set
  1029. # of classes. Every class is identified by a single character:
  1030. #
  1031. #  K     Keyspace events, published with __keyspace@<db>__ prefix.
  1032. #  E     Keyevent events, published with __keyevent@<db>__ prefix.
  1033. #  g     Generic commands (non-type specific) like DEL, EXPIRE, RENAME, ...
  1034. #  $     String commands
  1035. #  l     List commands
  1036. #  s     Set commands
  1037. #  h     Hash commands
  1038. #  z     Sorted set commands
  1039. #  x     Expired events (events generated every time a key expires)
  1040. #  e     Evicted events (events generated when a key is evicted for maxmemory)
  1041. #  A     Alias for g$lshzxe, so that the "AKE" string means all the events.
  1042. #
  1043. #  The "notify-keyspace-events" takes as argument a string that is composed
  1044. #  of zero or multiple characters. The empty string means that notifications
  1045. #  are disabled.
  1046. #
  1047. #  Example: to enable list and generic events, from the point of view of the
  1048. #           event name, use:
  1049. #
  1050. #  notify-keyspace-events Elg
  1051. #
  1052. #  Example 2: to get the stream of the expired keys subscribing to channel
  1053. #             name __keyevent@0__:expired use:
  1054. #
  1055. #  notify-keyspace-events Ex
  1056. #
  1057. #  By default all notifications are disabled because most users don't need
  1058. #  this feature and the feature has some overhead. Note that if you don't
  1059. #  specify at least one of K or E, no events will be delivered.
  1060. notify-keyspace-events ""
  1062. ############################### ADVANCED CONFIG ###############################
  1064. # Hashes are encoded using a memory efficient data structure when they have a
  1065. # small number of entries, and the biggest entry does not exceed a given
  1066. # threshold. These thresholds can be configured using the following directives.
  1067. hash-max-ziplist-entries 512
  1068. hash-max-ziplist-value 64
  1070. # Lists are also encoded in a special way to save a lot of space.
  1071. # The number of entries allowed per internal list node can be specified
  1072. # as a fixed maximum size or a maximum number of elements.
  1073. # For a fixed maximum size, use -5 through -1, meaning:
  1074. # -5: max size: 64 Kb  <-- not recommended for normal workloads
  1075. # -4: max size: 32 Kb  <-- not recommended
  1076. # -3: max size: 16 Kb  <-- probably not recommended
  1077. # -2: max size: 8 Kb   <-- good
  1078. # -1: max size: 4 Kb   <-- good
  1079. # Positive numbers mean store up to _exactly_ that number of elements
  1080. # per list node.
  1081. # The highest performing option is usually -2 (8 Kb size) or -1 (4 Kb size),
  1082. # but if your use case is unique, adjust the settings as necessary.
  1083. list-max-ziplist-size -2
  1085. # Lists may also be compressed.
  1086. # Compress depth is the number of quicklist ziplist nodes from *each* side of
  1087. # the list to *exclude* from compression.  The head and tail of the list
  1088. # are always uncompressed for fast push/pop operations.  Settings are:
  1089. # 0: disable all list compression
  1090. # 1: depth 1 means "don't start compressing until after 1 node into the list,
  1091. #    going from either the head or tail"
  1092. #    So: [head]->node->node->...->node->[tail]
  1093. #    [head], [tail] will always be uncompressed; inner nodes will compress.
  1094. # 2: [head]->[next]->node->node->...->node->[prev]->[tail]
  1095. #    2 here means: don't compress head or head->next or tail->prev or tail,
  1096. #    but compress all nodes between them.
  1097. # 3: [head]->[next]->[next]->node->node->...->node->[prev]->[prev]->[tail]
  1098. # etc.
  1099. list-compress-depth 0
  1101. # Sets have a special encoding in just one case: when a set is composed
  1102. # of just strings that happen to be integers in radix 10 in the range
  1103. # of 64 bit signed integers.
  1104. # The following configuration setting sets the limit in the size of the
  1105. # set in order to use this special memory saving encoding.
  1106. set-max-intset-entries 512
  1108. # Similarly to hashes and lists, sorted sets are also specially encoded in
  1109. # order to save a lot of space. This encoding is only used when the length and
  1110. # elements of a sorted set are below the following limits:
  1111. zset-max-ziplist-entries 128
  1112. zset-max-ziplist-value 64
  1114. # HyperLogLog sparse representation bytes limit. The limit includes the
  1115. # 16 bytes header. When an HyperLogLog using the sparse representation crosses
  1116. # this limit, it is converted into the dense representation.
  1117. #
  1118. # A value greater than 16000 is totally useless, since at that point the
  1119. # dense representation is more memory efficient.
  1120. #
  1121. # The suggested value is ~ 3000 in order to have the benefits of
  1122. # the space efficient encoding without slowing down too much PFADD,
  1123. # which is O(N) with the sparse encoding. The value can be raised to
  1124. # ~ 10000 when CPU is not a concern, but space is, and the data set is
  1125. # composed of many HyperLogLogs with cardinality in the 0 - 15000 range.
  1126. hll-sparse-max-bytes 3000
  1128. # Streams macro node max size / items. The stream data structure is a radix
  1129. # tree of big nodes that encode multiple items inside. Using this configuration
  1130. # it is possible to configure how big a single node can be in bytes, and the
  1131. # maximum number of items it may contain before switching to a new node when
  1132. # appending new stream entries. If any of the following settings are set to
  1133. # zero, the limit is ignored, so for instance it is possible to set just a
  1134. # max entires limit by setting max-bytes to 0 and max-entries to the desired
  1135. # value.
  1136. stream-node-max-bytes 4096
  1137. stream-node-max-entries 100
  1139. # Active rehashing uses 1 millisecond every 100 milliseconds of CPU time in
  1140. # order to help rehashing the main Redis hash table (the one mapping top-level
  1141. # keys to values). The hash table implementation Redis uses (see dict.c)
  1142. # performs a lazy rehashing: the more operation you run into a hash table
  1143. # that is rehashing, the more rehashing "steps" are performed, so if the
  1144. # server is idle the rehashing is never complete and some more memory is used
  1145. # by the hash table.
  1146. #
  1147. # The default is to use this millisecond 10 times every second in order to
  1148. # actively rehash the main dictionaries, freeing memory when possible.
  1149. #
  1150. # If unsure:
  1151. # use "activerehashing no" if you have hard latency requirements and it is
  1152. # not a good thing in your environment that Redis can reply from time to time
  1153. # to queries with 2 milliseconds delay.
  1154. #
  1155. # use "activerehashing yes" if you don't have such hard requirements but
  1156. # want to free memory asap when possible.
  1157. activerehashing yes
  1159. # The client output buffer limits can be used to force disconnection of clients
  1160. # that are not reading data from the server fast enough for some reason (a
  1161. # common reason is that a Pub/Sub client can't consume messages as fast as the
  1162. # publisher can produce them).
  1163. #
  1164. # The limit can be set differently for the three different classes of clients:
  1165. #
  1166. # normal -> normal clients including MONITOR clients
  1167. # replica  -> replica clients
  1168. # pubsub -> clients subscribed to at least one pubsub channel or pattern
  1169. #
  1170. # The syntax of every client-output-buffer-limit directive is the following:
  1171. #
  1172. # client-output-buffer-limit <class> <hard limit> <soft limit> <soft seconds>
  1173. #
  1174. # A client is immediately disconnected once the hard limit is reached, or if
  1175. # the soft limit is reached and remains reached for the specified number of
  1176. # seconds (continuously).
  1177. # So for instance if the hard limit is 32 megabytes and the soft limit is
  1178. # 16 megabytes / 10 seconds, the client will get disconnected immediately
  1179. # if the size of the output buffers reach 32 megabytes, but will also get
  1180. # disconnected if the client reaches 16 megabytes and continuously overcomes
  1181. # the limit for 10 seconds.
  1182. #
  1183. # By default normal clients are not limited because they don't receive data
  1184. # without asking (in a push way), but just after a request, so only
  1185. # asynchronous clients may create a scenario where data is requested faster
  1186. # than it can read.
  1187. #
  1188. # Instead there is a default limit for pubsub and replica clients, since
  1189. # subscribers and replicas receive data in a push fashion.
  1190. #
  1191. # Both the hard or the soft limit can be disabled by setting them to zero.
  1192. client-output-buffer-limit normal 0 0 0
  1193. client-output-buffer-limit replica 256mb 64mb 60
  1194. client-output-buffer-limit pubsub 32mb 8mb 60
  1196. # Client query buffers accumulate new commands. They are limited to a fixed
  1197. # amount by default in order to avoid that a protocol desynchronization (for
  1198. # instance due to a bug in the client) will lead to unbound memory usage in
  1199. # the query buffer. However you can configure it here if you have very special
  1200. # needs, such us huge multi/exec requests or alike.
  1201. #
  1202. # client-query-buffer-limit 1gb
  1204. # In the Redis protocol, bulk requests, that are, elements representing single
  1205. # strings, are normally limited ot 512 mb. However you can change this limit
  1206. # here.
  1207. #
  1208. # proto-max-bulk-len 512mb
  1210. # Redis calls an internal function to perform many background tasks, like
  1211. # closing connections of clients in timeout, purging expired keys that are
  1212. # never requested, and so forth.
  1213. #
  1214. # Not all tasks are performed with the same frequency, but Redis checks for
  1215. # tasks to perform according to the specified "hz" value.
  1216. #
  1217. # By default "hz" is set to 10. Raising the value will use more CPU when
  1218. # Redis is idle, but at the same time will make Redis more responsive when
  1219. # there are many keys expiring at the same time, and timeouts may be
  1220. # handled with more precision.
  1221. #
  1222. # The range is between 1 and 500, however a value over 100 is usually not
  1223. # a good idea. Most users should use the default of 10 and raise this up to
  1224. # 100 only in environments where very low latency is required.
  1225. hz 10
  1227. # Normally it is useful to have an HZ value which is proportional to the
  1228. # number of clients connected. This is useful in order, for instance, to
  1229. # avoid too many clients are processed for each background task invocation
  1230. # in order to avoid latency spikes.
  1231. #
  1232. # Since the default HZ value by default is conservatively set to 10, Redis
  1233. # offers, and enables by default, the ability to use an adaptive HZ value
  1234. # which will temporary raise when there are many connected clients.
  1235. #
  1236. # When dynamic HZ is enabled, the actual configured HZ will be used as
  1237. # as a baseline, but multiples of the configured HZ value will be actually
  1238. # used as needed once more clients are connected. In this way an idle
  1239. # instance will use very little CPU time while a busy instance will be
  1240. # more responsive.
  1241. dynamic-hz yes
  1243. # When a child rewrites the AOF file, if the following option is enabled
  1244. # the file will be fsync-ed every 32 MB of data generated. This is useful
  1245. # in order to commit the file to the disk more incrementally and avoid
  1246. # big latency spikes.
  1247. aof-rewrite-incremental-fsync yes
  1249. # When redis saves RDB file, if the following option is enabled
  1250. # the file will be fsync-ed every 32 MB of data generated. This is useful
  1251. # in order to commit the file to the disk more incrementally and avoid
  1252. # big latency spikes.
  1253. rdb-save-incremental-fsync yes
  1255. # Redis LFU eviction (see maxmemory setting) can be tuned. However it is a good
  1256. # idea to start with the default settings and only change them after investigating
  1257. # how to improve the performances and how the keys LFU change over time, which
  1258. # is possible to inspect via the OBJECT FREQ command.
  1259. #
  1260. # There are two tunable parameters in the Redis LFU implementation: the
  1261. # counter logarithm factor and the counter decay time. It is important to
  1262. # understand what the two parameters mean before changing them.
  1263. #
  1264. # The LFU counter is just 8 bits per key, it's maximum value is 255, so Redis
  1265. # uses a probabilistic increment with logarithmic behavior. Given the value
  1266. # of the old counter, when a key is accessed, the counter is incremented in
  1267. # this way:
  1268. #
  1269. # 1. A random number R between 0 and 1 is extracted.
  1270. # 2. A probability P is calculated as 1/(old_value*lfu_log_factor+1).
  1271. # 3. The counter is incremented only if R < P.
  1272. #
  1273. # The default lfu-log-factor is 10. This is a table of how the frequency
  1274. # counter changes with a different number of accesses with different
  1275. # logarithmic factors:
  1276. #
  1277. # +--------+------------+------------+------------+------------+------------+
  1278. # | factor | 100 hits   | 1000 hits  | 100K hits  | 1M hits    | 10M hits   |
  1279. # +--------+------------+------------+------------+------------+------------+
  1280. # | 0      | 104        | 255        | 255        | 255        | 255        |
  1281. # +--------+------------+------------+------------+------------+------------+
  1282. # | 1      | 18         | 49         | 255        | 255        | 255        |
  1283. # +--------+------------+------------+------------+------------+------------+
  1284. # | 10     | 10         | 18         | 142        | 255        | 255        |
  1285. # +--------+------------+------------+------------+------------+------------+
  1286. # | 100    | 8          | 11         | 49         | 143        | 255        |
  1287. # +--------+------------+------------+------------+------------+------------+
  1288. #
  1289. # NOTE: The above table was obtained by running the following commands:
  1290. #
  1291. #   redis-benchmark -n 1000000 incr foo
  1292. #   redis-cli object freq foo
  1293. #
  1294. # NOTE 2: The counter initial value is 5 in order to give new objects a chance
  1295. # to accumulate hits.
  1296. #
  1297. # The counter decay time is the time, in minutes, that must elapse in order
  1298. # for the key counter to be divided by two (or decremented if it has a value
  1299. # less <= 10).
  1300. #
  1301. # The default value for the lfu-decay-time is 1. A Special value of 0 means to
  1302. # decay the counter every time it happens to be scanned.
  1303. #
  1304. # lfu-log-factor 10
  1305. # lfu-decay-time 1
  1307. ########################### ACTIVE DEFRAGMENTATION #######################
  1308. #
  1309. # WARNING THIS FEATURE IS EXPERIMENTAL. However it was stress tested
  1310. # even in production and manually tested by multiple engineers for some
  1311. # time.
  1312. #
  1313. # What is active defragmentation?
  1314. # -------------------------------
  1315. #
  1316. # Active (online) defragmentation allows a Redis server to compact the
  1317. # spaces left between small allocations and deallocations of data in memory,
  1318. # thus allowing to reclaim back memory.
  1319. #
  1320. # Fragmentation is a natural process that happens with every allocator (but
  1321. # less so with Jemalloc, fortunately) and certain workloads. Normally a server
  1322. # restart is needed in order to lower the fragmentation, or at least to flush
  1323. # away all the data and create it again. However thanks to this feature
  1324. # implemented by Oran Agra for Redis 4.0 this process can happen at runtime
  1325. # in an "hot" way, while the server is running.
  1326. #
  1327. # Basically when the fragmentation is over a certain level (see the
  1328. # configuration options below) Redis will start to create new copies of the
  1329. # values in contiguous memory regions by exploiting certain specific Jemalloc
  1330. # features (in order to understand if an allocation is causing fragmentation
  1331. # and to allocate it in a better place), and at the same time, will release the
  1332. # old copies of the data. This process, repeated incrementally for all the keys
  1333. # will cause the fragmentation to drop back to normal values.
  1334. #
  1335. # Important things to understand:
  1336. #
  1337. # 1. This feature is disabled by default, and only works if you compiled Redis
  1338. #    to use the copy of Jemalloc we ship with the source code of Redis.
  1339. #    This is the default with Linux builds.
  1340. #
  1341. # 2. You never need to enable this feature if you don't have fragmentation
  1342. #    issues.
  1343. #
  1344. # 3. Once you experience fragmentation, you can enable this feature when
  1345. #    needed with the command "CONFIG SET activedefrag yes".
  1346. #
  1347. # The configuration parameters are able to fine tune the behavior of the
  1348. # defragmentation process. If you are not sure about what they mean it is
  1349. # a good idea to leave the defaults untouched.
  1351. # Enabled active defragmentation
  1352. # activedefrag yes
  1354. # Minimum amount of fragmentation waste to start active defrag
  1355. # active-defrag-ignore-bytes 100mb
  1357. # Minimum percentage of fragmentation to start active defrag
  1358. # active-defrag-threshold-lower 10
  1360. # Maximum percentage of fragmentation at which we use maximum effort
  1361. # active-defrag-threshold-upper 100
  1363. # Minimal effort for defrag in CPU percentage
  1364. # active-defrag-cycle-min 5
  1366. # Maximal effort for defrag in CPU percentage
  1367. # active-defrag-cycle-max 75
  1369. # Maximum number of set/hash/zset/list fields that will be processed from
  1370. # the main dictionary scan
  1371. # active-defrag-max-scan-fields 1000

Version 6.05

  1. # 当配置中需要配置内存大小时，可以使用 1k, 5GB, 4M 等类似的格式，其转换方式如下(不区分大小写)
  2. #
  3. # 1k => 1000 bytes
  4. # 1kb => 1024 bytes
  5. # 1m => 1000000 bytes
  6. # 1mb => 1024*1024 bytes
  7. # 1g => 1000000000 bytes
  8. # 1gb => 1024*1024*1024 bytes
  9. #
  10. # 内存配置大小写是一样的.比如 1gb 1Gb 1GB 1gB
  13. # daemonize no 默认情况下，redis不是在后台运行的，如果需要在后台运行，把该项的值更改为yes
  14. daemonize yes
  16. # 当redis在后台运行的时候，Redis默认会把pid文件放在/var/run/redis.pid，你可以配置到其他地址。
  17. # 当运行多个redis服务时，需要指定不同的pid文件和端口
  18. pidfile /var/run/redis.pid
  20. # 指定redis运行的端口，默认是6379
  21. port 6379
  23. # 指定redis只接收来自于该IP地址的请求，如果不进行设置，那么将处理所有请求，
  24. # 在生产环境中最好设置该项
  25. # bind 127.0.0.1
  27. # Specify the path for the unix socket that will be used to listen for
  28. # incoming connections. There is no default, so Redis will not listen
  29. # on a unix socket when not specified.
  30. #
  31. # unixsocket /tmp/redis.sock
  32. # unixsocketperm 755
  34. # 设置客户端连接时的超时时间，单位为秒。当客户端在这段时间内没有发出任何指令，那么关闭该连接
  35. # 0是关闭此设置
  36. timeout 0
  38. # 指定日志记录级别
  39. # Redis总共支持四个级别：debug、verbose、notice、warning，默认为verbose
  40. # debug 记录很多信息，用于开发和测试
  41. # varbose 有用的信息，不像debug会记录那么多
  42. # notice 普通的verbose，常用于生产环境
  43. # warning 只有非常重要或者严重的信息会记录到日志
  44. loglevel debug
  46. # 配置log文件地址
  47. # 默认值为stdout，标准输出，若后台模式会输出到/dev/null
  48. #logfile stdout
  49. logfile /var/log/redis/redis.log
  51. # To enable logging to the system logger, just set 'syslog-enabled' to yes,
  52. # and optionally update the other syslog parameters to suit your needs.
  53. # syslog-enabled no
  55. # Specify the syslog identity.
  56. # syslog-ident redis
  58. # Specify the syslog facility.  Must be USER or between LOCAL0-LOCAL7.
  59. # syslog-facility local0
  61. # 可用数据库数
  62. # 默认值为16，默认数据库为0，数据库范围在0-（database-1）之间
  63. databases 16
  65. ################################ 快照  #################################
  66. #
  67. # 保存数据到磁盘，格式如下:
  68. #
  69. #   save <seconds> <changes>
  70. #
  71. #   指出在多长时间内，有多少次更新操作，就将数据同步到数据文件rdb。
  72. #   相当于条件触发抓取快照，这个可以多个条件配合
  73. #   
  74. #   比如默认配置文件中的设置，就设置了三个条件
  75. #
  76. #   save 900 1  900秒内至少有1个key被改变
  77. #   save 300 10  300秒内至少有300个key被改变
  78. #   save 60 10000  60秒内至少有10000个key被改变
  80. save 900 1
  81. save 300 10
  82. save 60 10000
  84. # 存储至本地数据库时（持久化到rdb文件）是否压缩数据，默认为yes
  85. rdbcompression yes
  88. # 本地持久化数据库文件名，默认值为dump.rdb
  89. dbfilename dump.rdb
  91. # 工作目录
  92. #
  93. # 数据库镜像备份的文件放置的路径。
  94. # 这里的路径跟文件名要分开配置是因为redis在进行备份时，先会将当前数据库的状态写入到一个临时文件中，等备份完成时，
  95. # 再把该该临时文件替换为上面所指定的文件，而这里的临时文件和上面所配置的备份文件都会放在这个指定的路径当中。
  96. #
  97. # AOF文件也会存放在这个目录下面
  98. #
  99. # 注意这里必须制定一个目录而不是文件
  100. dir ./
  102. ################################# 复制 #################################
  104. # 主从复制. 设置该数据库为其他数据库的从数据库.
  105. # 设置当本机为slav服务时，设置master服务的IP地址及端口，在Redis启动时，它会自动从master进行数据同步
  106. #
  107. # slaveof <masterip> <masterport>
  109. # 当master服务设置了密码保护时(用requirepass制定的密码)
  110. # slav服务连接master的密码
  111. #
  112. # masterauth <master-password>
  115. # 当从库同主机失去连接或者复制正在进行，从机库有两种运行方式：
  116. #
  117. # 1) 如果slave-serve-stale-data设置为yes(默认设置)，从库会继续相应客户端的请求
  118. #
  119. # 2) 如果slave-serve-stale-data是指为no，出去INFO和SLAVOF命令之外的任何请求都会返回一个
  120. #    错误"SYNC with master in progress"
  121. #
  122. slave-serve-stale-data yes
  124. # 从库会按照一个时间间隔向主库发送PINGs.可以通过repl-ping-slave-period设置这个时间间隔，默认是10秒
  125. #
  126. # repl-ping-slave-period 10
  128. # repl-timeout 设置主库批量数据传输时间或者ping回复时间间隔，默认值是60秒
  129. # 一定要确保repl-timeout大于repl-ping-slave-period
  130. # repl-timeout 60
  132. ################################## 安全 ###################################
  134. # 设置客户端连接后进行任何其他指定前需要使用的密码。
  135. # 警告：因为redis速度相当快，所以在一台比较好的服务器下，一个外部的用户可以在一秒钟进行150K次的密码尝试，这意味着你需要指定非常非常强大的密码来防止暴力破解
  136. #
  137. # requirepass foobared
  139. # 命令重命名.
  140. #
  141. # 在一个共享环境下可以重命名相对危险的命令。比如把CONFIG重名为一个不容易猜测的字符。
  142. #
  143. # 举例:
  144. #
  145. # rename-command CONFIG b840fc02d524045429941cc15f59e41cb7be6c52
  146. #
  147. # 如果想删除一个命令，直接把它重命名为一个空字符""即可，如下：
  148. #
  149. # rename-command CONFIG ""
  151. ################################### 约束 ####################################
  153. # 设置同一时间最大客户端连接数，默认无限制，Redis可以同时打开的客户端连接数为Redis进程可以打开的最大文件描述符数，
  154. # 如果设置 maxclients 0，表示不作限制。
  155. # 当客户端连接数到达限制时，Redis会关闭新的连接并向客户端返回max number of clients reached错误信息
  156. #
  157. # maxclients 128
  159. # 指定Redis最大内存限制，Redis在启动时会把数据加载到内存中，达到最大内存后，Redis会先尝试清除已到期或即将到期的Key
  160. # Redis同时也会移除空的list对象
  161. #
  162. # 当此方法处理后，仍然到达最大内存设置，将无法再进行写入操作，但仍然可以进行读取操作
  163. #
  164. # 注意：Redis新的vm机制，会把Key存放内存，Value会存放在swap区
  165. #
  166. # maxmemory的设置比较适合于把redis当作于类似memcached的缓存来使用，而不适合当做一个真实的DB。
  167. # 当把Redis当做一个真实的数据库使用的时候，内存使用将是一个很大的开销
  168. # maxmemory <bytes>
  170. # 当内存达到最大值的时候Redis会选择删除哪些数据？有五种方式可供选择
  171. #
  172. # volatile-lru -> 利用LRU算法移除设置过过期时间的key (LRU:最近使用 Least Recently Used )
  173. # allkeys-lru -> 利用LRU算法移除任何key
  174. # volatile-random -> 移除设置过过期时间的随机key
  175. # allkeys->random -> remove a random key, any key
  176. # volatile-ttl -> 移除即将过期的key(minor TTL)
  177. # noeviction -> 不移除任何可以，只是返回一个写错误
  178. #
  179. # 注意：对于上面的策略，如果没有合适的key可以移除，当写的时候Redis会返回一个错误
  180. #
  181. #       写命令包括: set setnx setex append
  182. #       incr decr rpush lpush rpushx lpushx linsert lset rpoplpush sadd
  183. #       sinter sinterstore sunion sunionstore sdiff sdiffstore zadd zincrby
  184. #       zunionstore zinterstore hset hsetnx hmset hincrby incrby decrby
  185. #       getset mset msetnx exec sort
  186. #
  187. # 默认是:
  188. #
  189. # maxmemory-policy volatile-lru
  191. # LRU 和 minimal TTL 算法都不是精准的算法，但是相对精确的算法(为了节省内存)，随意你可以选择样本大小进行检测。
  192. # Redis默认的灰选择3个样本进行检测，你可以通过maxmemory-samples进行设置
  193. #
  194. # maxmemory-samples 3
  196. ############################## AOF ###############################
  198. # 默认情况下，redis会在后台异步的把数据库镜像备份到磁盘，但是该备份是非常耗时的，而且备份也不能很频繁，如果发生诸如拉闸限电、拔插头等状况，那么将造成比较大范围的数据丢失。
  199. # 所以redis提供了另外一种更加高效的数据库备份及灾难恢复方式。
  200. # 开启append only模式之后，redis会把所接收到的每一次写操作请求都追加到appendonly.aof文件中，当redis重新启动时，会从该文件恢复出之前的状态。
  201. # 但是这样会造成appendonly.aof文件过大，所以redis还支持了BGREWRITEAOF指令，对appendonly.aof 进行重新整理。
  202. # 你可以同时开启asynchronous dumps 和 AOF
  204. appendonly no
  206. # AOF文件名称 (默认: "appendonly.aof")
  207. # appendfilename appendonly.aof
  210. # Redis支持三种同步AOF文件的策略:
  211. #
  212. # no: 不进行同步，系统去操作 . Faster.
  213. # always: always表示每次有写操作都进行同步. Slow, Safest.
  214. # everysec: 表示对写操作进行累积，每秒同步一次. Compromise.
  215. #
  216. # 默认是"everysec"，按照速度和安全折中这是最好的。
  217. # 如果想让Redis能更高效的运行，你也可以设置为"no"，让操作系统决定什么时候去执行
  218. # 或者相反想让数据更安全你也可以设置为"always"
  219. #
  220. # 如果不确定就用 "everysec".
  222. # appendfsync always
  223. appendfsync everysec
  224. # appendfsync no
  226. # AOF策略设置为always或者everysec时，后台处理进程(后台保存或者AOF日志重写)会执行大量的I/O操作
  227. # 在某些Linux配置中会阻止过长的fsync()请求。注意现在没有任何修复，即使fsync在另外一个线程进行处理
  228. #
  229. # 为了减缓这个问题，可以设置下面这个参数no-appendfsync-on-rewrite
  230. #
  231. # This means that while another child is saving the durability of Redis is
  232. # the same as "appendfsync none", that in pratical terms means that it is
  233. # possible to lost up to 30 seconds of log in the worst scenario (with the
  234. # default Linux settings).
  235. #
  236. # If you have latency problems turn this to "yes". Otherwise leave it as
  237. # "no" that is the safest pick from the point of view of durability.
  238. no-appendfsync-on-rewrite no
  240. # Automatic rewrite of the append only file.
  241. # AOF 自动重写
  242. # 当AOF文件增长到一定大小的时候Redis能够调用 BGREWRITEAOF 对日志文件进行重写
  243. #
  244. # 它是这样工作的：Redis会记住上次进行些日志后文件的大小(如果从开机以来还没进行过重写，那日子大小在开机的时候确定)
  245. #
  246. # 基础大小会同现在的大小进行比较。如果现在的大小比基础大小大制定的百分比，重写功能将启动
  247. # 同时需要指定一个最小大小用于AOF重写，这个用于阻止即使文件很小但是增长幅度很大也去重写AOF文件的情况
  248. # 设置 percentage 为0就关闭这个特性
  251. auto-aof-rewrite-percentage 100
  252. auto-aof-rewrite-min-size 64mb
  254. ################################## SLOW LOG ###################################
  256. # Redis Slow Log 记录超过特定执行时间的命令。执行时间不包括I/O计算比如连接客户端，返回结果等，只是命令执行时间
  257. #
  258. # 可以通过两个参数设置slow log：一个是告诉Redis执行超过多少时间被记录的参数slowlog-log-slower-than(微妙)，
  259. # 另一个是slow log 的长度。当一个新命令被记录的时候最早的命令将被从队列中移除
  262. # 下面的时间以微妙微单位，因此1000000代表一分钟。
  263. # 注意制定一个负数将关闭慢日志，而设置为0将强制每个命令都会记录
  264. slowlog-log-slower-than 10000
  267. # 对日志长度没有限制，只是要注意它会消耗内存
  268. # 可以通过 SLOWLOG RESET 回收被慢日志消耗的内存
  269. slowlog-max-len 1024
  271. ################################ VM ###############################
  273. ### WARNING! Virtual Memory is deprecated in Redis 2.4
  274. ### The use of Virtual Memory is strongly discouraged.
  276. # Virtual Memory allows Redis to work with datasets bigger than the actual
  277. # amount of RAM needed to hold the whole dataset in memory.
  278. # In order to do so very used keys are taken in memory while the other keys
  279. # are swapped into a swap file, similarly to what operating systems do
  280. # with memory pages.
  281. #
  282. # To enable VM just set 'vm-enabled' to yes, and set the following three
  283. # VM parameters accordingly to your needs.
  285. vm-enabled no
  286. # vm-enabled yes
  288. # This is the path of the Redis swap file. As you can guess, swap files
  289. # can't be shared by different Redis instances, so make sure to use a swap
  290. # file for every redis process you are running. Redis will complain if the
  291. # swap file is already in use.
  292. #
  293. # The best kind of storage for the Redis swap file (that's accessed at random)
  294. # is a Solid State Disk (SSD).
  295. #
  296. # *** WARNING *** if you are using a shared hosting the default of putting
  297. # the swap file under /tmp is not secure. Create a dir with access granted
  298. # only to Redis user and configure Redis to create the swap file there.
  299. vm-swap-file /tmp/redis.swap
  301. # vm-max-memory configures the VM to use at max the specified amount of
  302. # RAM. Everything that deos not fit will be swapped on disk *if* possible, that
  303. # is, if there is still enough contiguous space in the swap file.
  304. #
  305. # With vm-max-memory 0 the system will swap everything it can. Not a good
  306. # default, just specify the max amount of RAM you can in bytes, but it's
  307. # better to leave some margin. For instance specify an amount of RAM
  308. # that's more or less between 60 and 80% of your free RAM.
  309. vm-max-memory 0
  311. # Redis swap files is split into pages. An object can be saved using multiple
  312. # contiguous pages, but pages can't be shared between different objects.
  313. # So if your page is too big, small objects swapped out on disk will waste
  314. # a lot of space. If you page is too small, there is less space in the swap
  315. # file (assuming you configured the same number of total swap file pages).
  316. #
  317. # If you use a lot of small objects, use a page size of 64 or 32 bytes.
  318. # If you use a lot of big objects, use a bigger page size.
  319. # If unsure, use the default :)
  320. vm-page-size 32
  322. # Number of total memory pages in the swap file.
  323. # Given that the page table (a bitmap of free/used pages) is taken in memory,
  324. # every 8 pages on disk will consume 1 byte of RAM.
  325. #
  326. # The total swap size is vm-page-size * vm-pages
  327. #
  328. # With the default of 32-bytes memory pages and 134217728 pages Redis will
  329. # use a 4 GB swap file, that will use 16 MB of RAM for the page table.
  330. #
  331. # It's better to use the smallest acceptable value for your application,
  332. # but the default is large in order to work in most conditions.
  333. vm-pages 134217728
  335. # Max number of VM I/O threads running at the same time.
  336. # This threads are used to read/write data from/to swap file, since they
  337. # also encode and decode objects from disk to memory or the reverse, a bigger
  338. # number of threads can help with big objects even if they can't help with
  339. # I/O itself as the physical device may not be able to couple with many
  340. # reads/writes operations at the same time.
  341. #
  342. # The special value of 0 turn off threaded I/O and enables the blocking
  343. # Virtual Memory implementation.
  344. vm-max-threads 4
  346. ############################### ADVANCED CONFIG ###############################
  348. # 当hash中包含超过指定元素个数并且最大的元素没有超过临界时，
  349. # hash将以一种特殊的编码方式（大大减少内存使用）来存储，这里可以设置这两个临界值
  350. # Redis Hash对应Value内部实际就是一个HashMap，实际这里会有2种不同实现，
  351. # 这个Hash的成员比较少时Redis为了节省内存会采用类似一维数组的方式来紧凑存储，而不会采用真正的HashMap结构，对应的value redisObject的encoding为zipmap,
  352. # 当成员数量增大时会自动转成真正的HashMap,此时encoding为ht。
  353. hash-max-zipmap-entries 512
  354. hash-max-zipmap-value 64
  356. # list数据类型多少节点以下会采用去指针的紧凑存储格式。
  357. # list数据类型节点值大小小于多少字节会采用紧凑存储格式。
  358. list-max-ziplist-entries 512
  359. list-max-ziplist-value 64
  361. # set数据类型内部数据如果全部是数值型，且包含多少节点以下会采用紧凑格式存储。
  362. set-max-intset-entries 512
  364. # zsort数据类型多少节点以下会采用去指针的紧凑存储格式。
  365. # zsort数据类型节点值大小小于多少字节会采用紧凑存储格式。
  366. zset-max-ziplist-entries 128
  367. zset-max-ziplist-value 64
  370. # Redis将在每100毫秒时使用1毫秒的CPU时间来对redis的hash表进行重新hash，可以降低内存的使用
  371. #
  372. # 当你的使用场景中，有非常严格的实时性需要，不能够接受Redis时不时的对请求有2毫秒的延迟的话，把这项配置为no。
  373. #
  374. # 如果没有这么严格的实时性要求，可以设置为yes，以便能够尽可能快的释放内存
  375. activerehashing yes
  377. ################################## INCLUDES ###################################
  379. # 指定包含其它的配置文件，可以在同一主机上多个Redis实例之间使用同一份配置文件，而同时各个实例又拥有自己的特定配置文件
  381. # include /path/to/local.conf
  382. # include /path/to/other.conf
  383. ————————————————
  384. 版权声明：本文为CSDN博主「_yuki_」的原创文章，遵循CC 4.0 BY-SA版权协议，转载请附上原文出处链接及本声明。
  385. 原文链接：https://blog.csdn.net/qq_19707521/java/article/details/70676213
  1. # Redis configuration file example.
  2. #
  3. # Note that in order to read the configuration file, Redis must be
  4. # started with the file path as first argument:
  5. #
  6. # ./redis-server /path/to/redis.conf
  8. # Note on units: when memory size is needed, it is possible to specify
  9. # it in the usual form of 1k 5GB 4M and so forth:
  10. #
  11. # 1k => 1000 bytes
  12. # 1kb => 1024 bytes
  13. # 1m => 1000000 bytes
  14. # 1mb => 1024*1024 bytes
  15. # 1g => 1000000000 bytes
  16. # 1gb => 1024*1024*1024 bytes
  17. #
  18. # units are case insensitive so 1GB 1Gb 1gB are all the same.
  20. ################################## INCLUDES ###################################
  22. # Include one or more other config files here.  This is useful if you
  23. # have a standard template that goes to all Redis servers but also need
  24. # to customize a few per-server settings.  Include files can include
  25. # other files, so use this wisely.
  26. #
  27. # Notice option "include" won't be rewritten by command "CONFIG REWRITE"
  28. # from admin or Redis Sentinel. Since Redis always uses the last processed
  29. # line as value of a configuration directive, you'd better put includes
  30. # at the beginning of this file to avoid overwriting config change at runtime.
  31. #
  32. # If instead you are interested in using includes to override configuration
  33. # options, it is better to use include as the last line.
  34. #
  35. # include /path/to/local.conf
  36. # include /path/to/other.conf
  38. ################################## MODULES #####################################
  40. # Load modules at startup. If the server is not able to load modules
  41. # it will abort. It is possible to use multiple loadmodule directives.
  42. #
  43. # loadmodule /path/to/my_module.so
  44. # loadmodule /path/to/other_module.so
  46. ################################## NETWORK #####################################
  48. # By default, if no "bind" configuration directive is specified, Redis listens
  49. # for connections from all the network interfaces available on the server.
  50. # It is possible to listen to just one or multiple selected interfaces using
  51. # the "bind" configuration directive, followed by one or more IP addresses.
  52. #
  53. # Examples:
  54. #
  55. # bind 192.168.1.100 10.0.0.1
  56. # bind 127.0.0.1 ::1
  57. #
  58. # ~~~ WARNING ~~~ If the computer running Redis is directly exposed to the
  59. # internet, binding to all the interfaces is dangerous and will expose the
  60. # instance to everybody on the internet. So by default we uncomment the
  61. # following bind directive, that will force Redis to listen only into
  62. # the IPv4 loopback interface address (this means Redis will be able to
  63. # accept connections only from clients running into the same computer it
  64. # is running).
  65. #
  66. # IF YOU ARE SURE YOU WANT YOUR INSTANCE TO LISTEN TO ALL THE INTERFACES
  67. # JUST COMMENT THE FOLLOWING LINE.
  68. # ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  69. bind 127.0.0.1
  71. # Protected mode is a layer of security protection, in order to avoid that
  72. # Redis instances left open on the internet are accessed and exploited.
  73. #
  74. # When protected mode is on and if:
  75. #
  76. # 1) The server is not binding explicitly to a set of addresses using the
  77. #    "bind" directive.
  78. # 2) No password is configured.
  79. #
  80. # The server only accepts connections from clients connecting from the
  81. # IPv4 and IPv6 loopback addresses 127.0.0.1 and ::1, and from Unix domain
  82. # sockets.
  83. #
  84. # By default protected mode is enabled. You should disable it only if
  85. # you are sure you want clients from other hosts to connect to Redis
  86. # even if no authentication is configured, nor a specific set of interfaces
  87. # are explicitly listed using the "bind" directive.
  88. protected-mode yes
  90. # Accept connections on the specified port, default is 6379 (IANA #815344).
  91. # If port 0 is specified Redis will not listen on a TCP socket.
  92. port 6379
  94. # TCP listen() backlog.
  95. #
  96. # In high requests-per-second environments you need an high backlog in order
  97. # to avoid slow clients connections issues. Note that the Linux kernel
  98. # will silently truncate it to the value of /proc/sys/net/core/somaxconn so
  99. # make sure to raise both the value of somaxconn and tcp_max_syn_backlog
  100. # in order to get the desired effect.
  101. tcp-backlog 511
  103. # Unix socket.
  104. #
  105. # Specify the path for the Unix socket that will be used to listen for
  106. # incoming connections. There is no default, so Redis will not listen
  107. # on a unix socket when not specified.
  108. #
  109. # unixsocket /tmp/redis.sock
  110. # unixsocketperm 700
  112. # Close the connection after a client is idle for N seconds (0 to disable)
  113. timeout 0
  115. # TCP keepalive.
  116. #
  117. # If non-zero, use SO_KEEPALIVE to send TCP ACKs to clients in absence
  118. # of communication. This is useful for two reasons:
  119. #
  120. # 1) Detect dead peers.
  121. # 2) Take the connection alive from the point of view of network
  122. #    equipment in the middle.
  123. #
  124. # On Linux, the specified value (in seconds) is the period used to send ACKs.
  125. # Note that to close the connection the double of the time is needed.
  126. # On other kernels the period depends on the kernel configuration.
  127. #
  128. # A reasonable value for this option is 300 seconds, which is the new
  129. # Redis default starting with Redis 3.2.1.
  130. tcp-keepalive 300
  132. ################################# TLS/SSL #####################################
  134. # By default, TLS/SSL is disabled. To enable it, the "tls-port" configuration
  135. # directive can be used to define TLS-listening ports. To enable TLS on the
  136. # default port, use:
  137. #
  138. # port 0
  139. # tls-port 6379
  141. # Configure a X.509 certificate and private key to use for authenticating the
  142. # server to connected clients, masters or cluster peers.  These files should be
  143. # PEM formatted.
  144. #
  145. # tls-cert-file redis.crt 
  146. # tls-key-file redis.key
  148. # Configure a DH parameters file to enable Diffie-Hellman (DH) key exchange:
  149. #
  150. # tls-dh-params-file redis.dh
  152. # Configure a CA certificate(s) bundle or directory to authenticate TLS/SSL
  153. # clients and peers.  Redis requires an explicit configuration of at least one
  154. # of these, and will not implicitly use the system wide configuration.
  155. #
  156. # tls-ca-cert-file ca.crt
  157. # tls-ca-cert-dir /etc/ssl/certs
  159. # By default, clients (including replica servers) on a TLS port are required
  160. # to authenticate using valid client side certificates.
  161. #
  162. # It is possible to disable authentication using this directive.
  163. #
  164. # tls-auth-clients no
  166. # By default, a Redis replica does not attempt to establish a TLS connection
  167. # with its master.
  168. #
  169. # Use the following directive to enable TLS on replication links.
  170. #
  171. # tls-replication yes
  173. # By default, the Redis Cluster bus uses a plain TCP connection. To enable
  174. # TLS for the bus protocol, use the following directive:
  175. #
  176. # tls-cluster yes
  178. # Explicitly specify TLS versions to support. Allowed values are case insensitive
  179. # and include "TLSv1", "TLSv1.1", "TLSv1.2", "TLSv1.3" (OpenSSL >= 1.1.1) or
  180. # any combination. To enable only TLSv1.2 and TLSv1.3, use:
  181. #
  182. # tls-protocols "TLSv1.2 TLSv1.3"
  184. # Configure allowed ciphers.  See the ciphers(1ssl) manpage for more information
  185. # about the syntax of this string.
  186. #
  187. # Note: this configuration applies only to <= TLSv1.2.
  188. #
  189. # tls-ciphers DEFAULT:!MEDIUM
  191. # Configure allowed TLSv1.3 ciphersuites.  See the ciphers(1ssl) manpage for more
  192. # information about the syntax of this string, and specifically for TLSv1.3
  193. # ciphersuites.
  194. #
  195. # tls-ciphersuites TLS_CHACHA20_POLY1305_SHA256
  197. # When choosing a cipher, use the server's preference instead of the client
  198. # preference. By default, the server follows the client's preference.
  199. #
  200. # tls-prefer-server-ciphers yes
  202. ################################# GENERAL #####################################
  204. # By default Redis does not run as a daemon. Use 'yes' if you need it.
  205. # Note that Redis will write a pid file in /var/run/redis.pid when daemonized.
  206. daemonize no
  208. # If you run Redis from upstart or systemd, Redis can interact with your
  209. # supervision tree. Options:
  210. #   supervised no      - no supervision interaction
  211. #   supervised upstart - signal upstart by putting Redis into SIGSTOP mode
  212. #   supervised systemd - signal systemd by writing READY=1 to $NOTIFY_SOCKET
  213. #   supervised auto    - detect upstart or systemd method based on
  214. #                        UPSTART_JOB or NOTIFY_SOCKET environment variables
  215. # Note: these supervision methods only signal "process is ready."
  216. #       They do not enable continuous liveness pings back to your supervisor.
  217. supervised no
  219. # If a pid file is specified, Redis writes it where specified at startup
  220. # and removes it at exit.
  221. #
  222. # When the server runs non daemonized, no pid file is created if none is
  223. # specified in the configuration. When the server is daemonized, the pid file
  224. # is used even if not specified, defaulting to "/var/run/redis.pid".
  225. #
  226. # Creating a pid file is best effort: if Redis is not able to create it
  227. # nothing bad happens, the server will start and run normally.
  228. pidfile /var/run/redis_6379.pid
  230. # Specify the server verbosity level.
  231. # This can be one of:
  232. # debug (a lot of information, useful for development/testing)
  233. # verbose (many rarely useful info, but not a mess like the debug level)
  234. # notice (moderately verbose, what you want in production probably)
  235. # warning (only very important / critical messages are logged)
  236. loglevel notice
  238. # Specify the log file name. Also the empty string can be used to force
  239. # Redis to log on the standard output. Note that if you use standard
  240. # output for logging but daemonize, logs will be sent to /dev/null
  241. logfile ""
  243. # To enable logging to the system logger, just set 'syslog-enabled' to yes,
  244. # and optionally update the other syslog parameters to suit your needs.
  245. # syslog-enabled no
  247. # Specify the syslog identity.
  248. # syslog-ident redis
  250. # Specify the syslog facility. Must be USER or between LOCAL0-LOCAL7.
  251. # syslog-facility local0
  253. # Set the number of databases. The default database is DB 0, you can select
  254. # a different one on a per-connection basis using SELECT <dbid> where
  255. # dbid is a number between 0 and 'databases'-1
  256. databases 16
  258. # By default Redis shows an ASCII art logo only when started to log to the
  259. # standard output and if the standard output is a TTY. Basically this means
  260. # that normally a logo is displayed only in interactive sessions.
  261. #
  262. # However it is possible to force the pre-4.0 behavior and always show a
  263. # ASCII art logo in startup logs by setting the following option to yes.
  264. always-show-logo yes
  266. ################################ SNAPSHOTTING  ################################
  267. #
  268. # Save the DB on disk:
  269. #
  270. #   save <seconds> <changes>
  271. #
  272. #   Will save the DB if both the given number of seconds and the given
  273. #   number of write operations against the DB occurred.
  274. #
  275. #   In the example below the behaviour will be to save:
  276. #   after 900 sec (15 min) if at least 1 key changed
  277. #   after 300 sec (5 min) if at least 10 keys changed
  278. #   after 60 sec if at least 10000 keys changed
  279. #
  280. #   Note: you can disable saving completely by commenting out all "save" lines.
  281. #
  282. #   It is also possible to remove all the previously configured save
  283. #   points by adding a save directive with a single empty string argument
  284. #   like in the following example:
  285. #
  286. #   save ""
  288. save 900 1
  289. save 300 10
  290. save 60 10000
  292. # By default Redis will stop accepting writes if RDB snapshots are enabled
  293. # (at least one save point) and the latest background save failed.
  294. # This will make the user aware (in a hard way) that data is not persisting
  295. # on disk properly, otherwise chances are that no one will notice and some
  296. # disaster will happen.
  297. #
  298. # If the background saving process will start working again Redis will
  299. # automatically allow writes again.
  300. #
  301. # However if you have setup your proper monitoring of the Redis server
  302. # and persistence, you may want to disable this feature so that Redis will
  303. # continue to work as usual even if there are problems with disk,
  304. # permissions, and so forth.
  305. stop-writes-on-bgsave-error yes
  307. # Compress string objects using LZF when dump .rdb databases?
  308. # For default that's set to 'yes' as it's almost always a win.
  309. # If you want to save some CPU in the saving child set it to 'no' but
  310. # the dataset will likely be bigger if you have compressible values or keys.
  311. rdbcompression yes
  313. # Since version 5 of RDB a CRC64 checksum is placed at the end of the file.
  314. # This makes the format more resistant to corruption but there is a performance
  315. # hit to pay (around 10%) when saving and loading RDB files, so you can disable it
  316. # for maximum performances.
  317. #
  318. # RDB files created with checksum disabled have a checksum of zero that will
  319. # tell the loading code to skip the check.
  320. rdbchecksum yes
  322. # The filename where to dump the DB
  323. dbfilename dump.rdb
  325. # Remove RDB files used by replication in instances without persistence
  326. # enabled. By default this option is disabled, however there are environments
  327. # where for regulations or other security concerns, RDB files persisted on
  328. # disk by masters in order to feed replicas, or stored on disk by replicas
  329. # in order to load them for the initial synchronization, should be deleted
  330. # ASAP. Note that this option ONLY WORKS in instances that have both AOF
  331. # and RDB persistence disabled, otherwise is completely ignored.
  332. #
  333. # An alternative (and sometimes better) way to obtain the same effect is
  334. # to use diskless replication on both master and replicas instances. However
  335. # in the case of replicas, diskless is not always an option.
  336. rdb-del-sync-files no
  338. # The working directory.
  339. #
  340. # The DB will be written inside this directory, with the filename specified
  341. # above using the 'dbfilename' configuration directive.
  342. #
  343. # The Append Only File will also be created inside this directory.
  344. #
  345. # Note that you must specify a directory here, not a file name.
  346. dir ./
  348. ################################# REPLICATION #################################
  350. # Master-Replica replication. Use replicaof to make a Redis instance a copy of
  351. # another Redis server. A few things to understand ASAP about Redis replication.
  352. #
  353. #   +------------------+      +---------------+
  354. #   |      Master      | ---> |    Replica    |
  355. #   | (receive writes) |      |  (exact copy) |
  356. #   +------------------+      +---------------+
  357. #
  358. # 1) Redis replication is asynchronous, but you can configure a master to
  359. #    stop accepting writes if it appears to be not connected with at least
  360. #    a given number of replicas.
  361. # 2) Redis replicas are able to perform a partial resynchronization with the
  362. #    master if the replication link is lost for a relatively small amount of
  363. #    time. You may want to configure the replication backlog size (see the next
  364. #    sections of this file) with a sensible value depending on your needs.
  365. # 3) Replication is automatic and does not need user intervention. After a
  366. #    network partition replicas automatically try to reconnect to masters
  367. #    and resynchronize with them.
  368. #
  369. # replicaof <masterip> <masterport>
  371. # If the master is password protected (using the "requirepass" configuration
  372. # directive below) it is possible to tell the replica to authenticate before
  373. # starting the replication synchronization process, otherwise the master will
  374. # refuse the replica request.
  375. #
  376. # masterauth <master-password>
  377. #
  378. # However this is not enough if you are using Redis ACLs (for Redis version
  379. # 6 or greater), and the default user is not capable of running the PSYNC
  380. # command and/or other commands needed for replication. In this case it's
  381. # better to configure a special user to use with replication, and specify the
  382. # masteruser configuration as such:
  383. #
  384. # masteruser <username>
  385. #
  386. # When masteruser is specified, the replica will authenticate against its
  387. # master using the new AUTH form: AUTH <username> <password>.
  389. # When a replica loses its connection with the master, or when the replication
  390. # is still in progress, the replica can act in two different ways:
  391. #
  392. # 1) if replica-serve-stale-data is set to 'yes' (the default) the replica will
  393. #    still reply to client requests, possibly with out of date data, or the
  394. #    data set may just be empty if this is the first synchronization.
  395. #
  396. # 2) if replica-serve-stale-data is set to 'no' the replica will reply with
  397. #    an error "SYNC with master in progress" to all the kind of commands
  398. #    but to INFO, replicaOF, AUTH, PING, SHUTDOWN, REPLCONF, ROLE, CONFIG,
  399. #    SUBSCRIBE, UNSUBSCRIBE, PSUBSCRIBE, PUNSUBSCRIBE, PUBLISH, PUBSUB,
  400. #    COMMAND, POST, HOST: and LATENCY.
  401. #
  402. replica-serve-stale-data yes
  404. # You can configure a replica instance to accept writes or not. Writing against
  405. # a replica instance may be useful to store some ephemeral data (because data
  406. # written on a replica will be easily deleted after resync with the master) but
  407. # may also cause problems if clients are writing to it because of a
  408. # misconfiguration.
  409. #
  410. # Since Redis 2.6 by default replicas are read-only.
  411. #
  412. # Note: read only replicas are not designed to be exposed to untrusted clients
  413. # on the internet. It's just a protection layer against misuse of the instance.
  414. # Still a read only replica exports by default all the administrative commands
  415. # such as CONFIG, DEBUG, and so forth. To a limited extent you can improve
  416. # security of read only replicas using 'rename-command' to shadow all the
  417. # administrative / dangerous commands.
  418. replica-read-only yes
  420. # Replication SYNC strategy: disk or socket.
  421. #
  422. # New replicas and reconnecting replicas that are not able to continue the
  423. # replication process just receiving differences, need to do what is called a
  424. # "full synchronization". An RDB file is transmitted from the master to the
  425. # replicas.
  426. #
  427. # The transmission can happen in two different ways:
  428. #
  429. # 1) Disk-backed: The Redis master creates a new process that writes the RDB
  430. #                 file on disk. Later the file is transferred by the parent
  431. #                 process to the replicas incrementally.
  432. # 2) Diskless: The Redis master creates a new process that directly writes the
  433. #              RDB file to replica sockets, without touching the disk at all.
  434. #
  435. # With disk-backed replication, while the RDB file is generated, more replicas
  436. # can be queued and served with the RDB file as soon as the current child
  437. # producing the RDB file finishes its work. With diskless replication instead
  438. # once the transfer starts, new replicas arriving will be queued and a new
  439. # transfer will start when the current one terminates.
  440. #
  441. # When diskless replication is used, the master waits a configurable amount of
  442. # time (in seconds) before starting the transfer in the hope that multiple
  443. # replicas will arrive and the transfer can be parallelized.
  444. #
  445. # With slow disks and fast (large bandwidth) networks, diskless replication
  446. # works better.
  447. repl-diskless-sync no
  449. # When diskless replication is enabled, it is possible to configure the delay
  450. # the server waits in order to spawn the child that transfers the RDB via socket
  451. # to the replicas.
  452. #
  453. # This is important since once the transfer starts, it is not possible to serve
  454. # new replicas arriving, that will be queued for the next RDB transfer, so the
  455. # server waits a delay in order to let more replicas arrive.
  456. #
  457. # The delay is specified in seconds, and by default is 5 seconds. To disable
  458. # it entirely just set it to 0 seconds and the transfer will start ASAP.
  459. repl-diskless-sync-delay 5
  461. # -----------------------------------------------------------------------------
  462. # WARNING: RDB diskless load is experimental. Since in this setup the replica
  463. # does not immediately store an RDB on disk, it may cause data loss during
  464. # failovers. RDB diskless load + Redis modules not handling I/O reads may also
  465. # cause Redis to abort in case of I/O errors during the initial synchronization
  466. # stage with the master. Use only if your do what you are doing.
  467. # -----------------------------------------------------------------------------
  468. #
  469. # Replica can load the RDB it reads from the replication link directly from the
  470. # socket, or store the RDB to a file and read that file after it was completely
  471. # recived from the master.
  472. #
  473. # In many cases the disk is slower than the network, and storing and loading
  474. # the RDB file may increase replication time (and even increase the master's
  475. # Copy on Write memory and salve buffers).
  476. # However, parsing the RDB file directly from the socket may mean that we have
  477. # to flush the contents of the current database before the full rdb was
  478. # received. For this reason we have the following options:
  479. #
  480. # "disabled"    - Don't use diskless load (store the rdb file to the disk first)
  481. # "on-empty-db" - Use diskless load only when it is completely safe.
  482. # "swapdb"      - Keep a copy of the current db contents in RAM while parsing
  483. #                 the data directly from the socket. note that this requires
  484. #                 sufficient memory, if you don't have it, you risk an OOM kill.
  485. repl-diskless-load disabled
  487. # Replicas send PINGs to server in a predefined interval. It's possible to
  488. # change this interval with the repl_ping_replica_period option. The default
  489. # value is 10 seconds.
  490. #
  491. # repl-ping-replica-period 10
  493. # The following option sets the replication timeout for:
  494. #
  495. # 1) Bulk transfer I/O during SYNC, from the point of view of replica.
  496. # 2) Master timeout from the point of view of replicas (data, pings).
  497. # 3) Replica timeout from the point of view of masters (REPLCONF ACK pings).
  498. #
  499. # It is important to make sure that this value is greater than the value
  500. # specified for repl-ping-replica-period otherwise a timeout will be detected
  501. # every time there is low traffic between the master and the replica.
  502. #
  503. # repl-timeout 60
  505. # Disable TCP_NODELAY on the replica socket after SYNC?
  506. #
  507. # If you select "yes" Redis will use a smaller number of TCP packets and
  508. # less bandwidth to send data to replicas. But this can add a delay for
  509. # the data to appear on the replica side, up to 40 milliseconds with
  510. # Linux kernels using a default configuration.
  511. #
  512. # If you select "no" the delay for data to appear on the replica side will
  513. # be reduced but more bandwidth will be used for replication.
  514. #
  515. # By default we optimize for low latency, but in very high traffic conditions
  516. # or when the master and replicas are many hops away, turning this to "yes" may
  517. # be a good idea.
  518. repl-disable-tcp-nodelay no
  520. # Set the replication backlog size. The backlog is a buffer that accumulates
  521. # replica data when replicas are disconnected for some time, so that when a
  522. # replica wants to reconnect again, often a full resync is not needed, but a
  523. # partial resync is enough, just passing the portion of data the replica
  524. # missed while disconnected.
  525. #
  526. # The bigger the replication backlog, the longer the time the replica can be
  527. # disconnected and later be able to perform a partial resynchronization.
  528. #
  529. # The backlog is only allocated once there is at least a replica connected.
  530. #
  531. # repl-backlog-size 1mb
  533. # After a master has no longer connected replicas for some time, the backlog
  534. # will be freed. The following option configures the amount of seconds that
  535. # need to elapse, starting from the time the last replica disconnected, for
  536. # the backlog buffer to be freed.
  537. #
  538. # Note that replicas never free the backlog for timeout, since they may be
  539. # promoted to masters later, and should be able to correctly "partially
  540. # resynchronize" with the replicas: hence they should always accumulate backlog.
  541. #
  542. # A value of 0 means to never release the backlog.
  543. #
  544. # repl-backlog-ttl 3600
  546. # The replica priority is an integer number published by Redis in the INFO
  547. # output. It is used by Redis Sentinel in order to select a replica to promote
  548. # into a master if the master is no longer working correctly.
  549. #
  550. # A replica with a low priority number is considered better for promotion, so
  551. # for instance if there are three replicas with priority 10, 100, 25 Sentinel
  552. # will pick the one with priority 10, that is the lowest.
  553. #
  554. # However a special priority of 0 marks the replica as not able to perform the
  555. # role of master, so a replica with priority of 0 will never be selected by
  556. # Redis Sentinel for promotion.
  557. #
  558. # By default the priority is 100.
  559. replica-priority 100
  561. # It is possible for a master to stop accepting writes if there are less than
  562. # N replicas connected, having a lag less or equal than M seconds.
  563. #
  564. # The N replicas need to be in "online" state.
  565. #
  566. # The lag in seconds, that must be <= the specified value, is calculated from
  567. # the last ping received from the replica, that is usually sent every second.
  568. #
  569. # This option does not GUARANTEE that N replicas will accept the write, but
  570. # will limit the window of exposure for lost writes in case not enough replicas
  571. # are available, to the specified number of seconds.
  572. #
  573. # For example to require at least 3 replicas with a lag <= 10 seconds use:
  574. #
  575. # min-replicas-to-write 3
  576. # min-replicas-max-lag 10
  577. #
  578. # Setting one or the other to 0 disables the feature.
  579. #
  580. # By default min-replicas-to-write is set to 0 (feature disabled) and
  581. # min-replicas-max-lag is set to 10.
  583. # A Redis master is able to list the address and port of the attached
  584. # replicas in different ways. For example the "INFO replication" section
  585. # offers this information, which is used, among other tools, by
  586. # Redis Sentinel in order to discover replica instances.
  587. # Another place where this info is available is in the output of the
  588. # "ROLE" command of a master.
  589. #
  590. # The listed IP and address normally reported by a replica is obtained
  591. # in the following way:
  592. #
  593. #   IP: The address is auto detected by checking the peer address
  594. #   of the socket used by the replica to connect with the master.
  595. #
  596. #   Port: The port is communicated by the replica during the replication
  597. #   handshake, and is normally the port that the replica is using to
  598. #   listen for connections.
  599. #
  600. # However when port forwarding or Network Address Translation (NAT) is
  601. # used, the replica may be actually reachable via different IP and port
  602. # pairs. The following two options can be used by a replica in order to
  603. # report to its master a specific set of IP and port, so that both INFO
  604. # and ROLE will report those values.
  605. #
  606. # There is no need to use both the options if you need to override just
  607. # the port or the IP address.
  608. #
  609. # replica-announce-ip 5.5.5.5
  610. # replica-announce-port 1234
  612. ############################### KEYS TRACKING #################################
  614. # Redis implements server assisted support for client side caching of values.
  615. # This is implemented using an invalidation table that remembers, using
  616. # 16 millions of slots, what clients may have certain subsets of keys. In turn
  617. # this is used in order to send invalidation messages to clients. Please
  618. # to understand more about the feature check this page:
  619. #
  620. #   https://redis.io/topics/client-side-caching
  621. #
  622. # When tracking is enabled for a client, all the read only queries are assumed
  623. # to be cached: this will force Redis to store information in the invalidation
  624. # table. When keys are modified, such information is flushed away, and
  625. # invalidation messages are sent to the clients. However if the workload is
  626. # heavily dominated by reads, Redis could use more and more memory in order
  627. # to track the keys fetched by many clients.
  628. #
  629. # For this reason it is possible to configure a maximum fill value for the
  630. # invalidation table. By default it is set to 1M of keys, and once this limit
  631. # is reached, Redis will start to evict keys in the invalidation table
  632. # even if they were not modified, just to reclaim memory: this will in turn
  633. # force the clients to invalidate the cached values. Basically the table
  634. # maximum size is a trade off between the memory you want to spend server
  635. # side to track information about who cached what, and the ability of clients
  636. # to retain cached objects in memory.
  637. #
  638. # If you set the value to 0, it means there are no limits, and Redis will
  639. # retain as many keys as needed in the invalidation table.
  640. # In the "stats" INFO section, you can find information about the number of
  641. # keys in the invalidation table at every given moment.
  642. #
  643. # Note: when key tracking is used in broadcasting mode, no memory is used
  644. # in the server side so this setting is useless.
  645. #
  646. # tracking-table-max-keys 1000000
  648. ################################## SECURITY ###################################
  650. # Warning: since Redis is pretty fast an outside user can try up to
  651. # 1 million passwords per second against a modern box. This means that you
  652. # should use very strong passwords, otherwise they will be very easy to break.
  653. # Note that because the password is really a shared secret between the client
  654. # and the server, and should not be memorized by any human, the password
  655. # can be easily a long string from /dev/urandom or whatever, so by using a
  656. # long and unguessable password no brute force attack will be possible.
  658. # Redis ACL users are defined in the following format:
  659. #
  660. #   user <username> ... acl rules ...
  661. #
  662. # For example:
  663. #
  664. #   user worker +@list +@connection ~jobs:* on >ffa9203c493aa99
  665. #
  666. # The special username "default" is used for new connections. If this user
  667. # has the "nopass" rule, then new connections will be immediately authenticated
  668. # as the "default" user without the need of any password provided via the
  669. # AUTH command. Otherwise if the "default" user is not flagged with "nopass"
  670. # the connections will start in not authenticated state, and will require
  671. # AUTH (or the HELLO command AUTH option) in order to be authenticated and
  672. # start to work.
  673. #
  674. # The ACL rules that describe what an user can do are the following:
  675. #
  676. #  on           Enable the user: it is possible to authenticate as this user.
  677. #  off          Disable the user: it's no longer possible to authenticate
  678. #               with this user, however the already authenticated connections
  679. #               will still work.
  680. #  +<command>   Allow the execution of that command
  681. #  -<command>   Disallow the execution of that command
  682. #  +@<category> Allow the execution of all the commands in such category
  683. #               with valid categories are like @admin, @set, @sortedset, ...
  684. #               and so forth, see the full list in the server.c file where
  685. #               the Redis command table is described and defined.
  686. #               The special category @all means all the commands, but currently
  687. #               present in the server, and that will be loaded in the future
  688. #               via modules.
  689. #  +<command>|subcommand    Allow a specific subcommand of an otherwise
  690. #                           disabled command. Note that this form is not
  691. #                           allowed as negative like -DEBUG|SEGFAULT, but
  692. #                           only additive starting with "+".
  693. #  allcommands  Alias for +@all. Note that it implies the ability to execute
  694. #               all the future commands loaded via the modules system.
  695. #  nocommands   Alias for -@all.
  696. #  ~<pattern>   Add a pattern of keys that can be mentioned as part of
  697. #               commands. For instance ~* allows all the keys. The pattern
  698. #               is a glob-style pattern like the one of KEYS.
  699. #               It is possible to specify multiple patterns.
  700. #  allkeys      Alias for ~*
  701. #  resetkeys    Flush the list of allowed keys patterns.
  702. #  ><password>  Add this passowrd to the list of valid password for the user.
  703. #               For example >mypass will add "mypass" to the list.
  704. #               This directive clears the "nopass" flag (see later).
  705. #  <<password>  Remove this password from the list of valid passwords.
  706. #  nopass       All the set passwords of the user are removed, and the user
  707. #               is flagged as requiring no password: it means that every
  708. #               password will work against this user. If this directive is
  709. #               used for the default user, every new connection will be
  710. #               immediately authenticated with the default user without
  711. #               any explicit AUTH command required. Note that the "resetpass"
  712. #               directive will clear this condition.
  713. #  resetpass    Flush the list of allowed passwords. Moreover removes the
  714. #               "nopass" status. After "resetpass" the user has no associated
  715. #               passwords and there is no way to authenticate without adding
  716. #               some password (or setting it as "nopass" later).
  717. #  reset        Performs the following actions: resetpass, resetkeys, off,
  718. #               -@all. The user returns to the same state it has immediately
  719. #               after its creation.
  720. #
  721. # ACL rules can be specified in any order: for instance you can start with
  722. # passwords, then flags, or key patterns. However note that the additive
  723. # and subtractive rules will CHANGE MEANING depending on the ordering.
  724. # For instance see the following example:
  725. #
  726. #   user alice on +@all -DEBUG ~* >somepassword
  727. #
  728. # This will allow "alice" to use all the commands with the exception of the
  729. # DEBUG command, since +@all added all the commands to the set of the commands
  730. # alice can use, and later DEBUG was removed. However if we invert the order
  731. # of two ACL rules the result will be different:
  732. #
  733. #   user alice on -DEBUG +@all ~* >somepassword
  734. #
  735. # Now DEBUG was removed when alice had yet no commands in the set of allowed
  736. # commands, later all the commands are added, so the user will be able to
  737. # execute everything.
  738. #
  739. # Basically ACL rules are processed left-to-right.
  740. #
  741. # For more information about ACL configuration please refer to
  742. # the Redis web site at https://redis.io/topics/acl
  744. # ACL LOG
  745. #
  746. # The ACL Log tracks failed commands and authentication events associated
  747. # with ACLs. The ACL Log is useful to troubleshoot failed commands blocked 
  748. # by ACLs. The ACL Log is stored in and consumes memory. There is no limit
  749. # to its length.You can reclaim memory with ACL LOG RESET or set a maximum
  750. # length below.
  751. acllog-max-len 128
  753. # Using an external ACL file
  754. #
  755. # Instead of configuring users here in this file, it is possible to use
  756. # a stand-alone file just listing users. The two methods cannot be mixed:
  757. # if you configure users here and at the same time you activate the exteranl
  758. # ACL file, the server will refuse to start.
  759. #
  760. # The format of the external ACL user file is exactly the same as the
  761. # format that is used inside redis.conf to describe users.
  762. #
  763. # aclfile /etc/redis/users.acl
  765. # IMPORTANT NOTE: starting with Redis 6 "requirepass" is just a compatiblity
  766. # layer on top of the new ACL system. The option effect will be just setting
  767. # the password for the default user. Clients will still authenticate using
  768. # AUTH <password> as usually, or more explicitly with AUTH default <password>
  769. # if they follow the new protocol: both will work.
  770. #
  771. # requirepass foobared
  773. # Command renaming (DEPRECATED).
  774. #
  775. # ------------------------------------------------------------------------
  776. # WARNING: avoid using this option if possible. Instead use ACLs to remove
  777. # commands from the default user, and put them only in some admin user you
  778. # create for administrative purposes.
  779. # ------------------------------------------------------------------------
  780. #
  781. # It is possible to change the name of dangerous commands in a shared
  782. # environment. For instance the CONFIG command may be renamed into something
  783. # hard to guess so that it will still be available for internal-use tools
  784. # but not available for general clients.
  785. #
  786. # Example:
  787. #
  788. # rename-command CONFIG b840fc02d524045429941cc15f59e41cb7be6c52
  789. #
  790. # It is also possible to completely kill a command by renaming it into
  791. # an empty string:
  792. #
  793. # rename-command CONFIG ""
  794. #
  795. # Please note that changing the name of commands that are logged into the
  796. # AOF file or transmitted to replicas may cause problems.
  798. ################################### CLIENTS ####################################
  800. # Set the max number of connected clients at the same time. By default
  801. # this limit is set to 10000 clients, however if the Redis server is not
  802. # able to configure the process file limit to allow for the specified limit
  803. # the max number of allowed clients is set to the current file limit
  804. # minus 32 (as Redis reserves a few file descriptors for internal uses).
  805. #
  806. # Once the limit is reached Redis will close all the new connections sending
  807. # an error 'max number of clients reached'.
  808. #
  809. # maxclients 10000
  811. ############################## MEMORY MANAGEMENT ################################
  813. # Set a memory usage limit to the specified amount of bytes.
  814. # When the memory limit is reached Redis will try to remove keys
  815. # according to the eviction policy selected (see maxmemory-policy).
  816. #
  817. # If Redis can't remove keys according to the policy, or if the policy is
  818. # set to 'noeviction', Redis will start to reply with errors to commands
  819. # that would use more memory, like SET, LPUSH, and so on, and will continue
  820. # to reply to read-only commands like GET.
  821. #
  822. # This option is usually useful when using Redis as an LRU or LFU cache, or to
  823. # set a hard memory limit for an instance (using the 'noeviction' policy).
  824. #
  825. # WARNING: If you have replicas attached to an instance with maxmemory on,
  826. # the size of the output buffers needed to feed the replicas are subtracted
  827. # from the used memory count, so that network problems / resyncs will
  828. # not trigger a loop where keys are evicted, and in turn the output
  829. # buffer of replicas is full with DELs of keys evicted triggering the deletion
  830. # of more keys, and so forth until the database is completely emptied.
  831. #
  832. # In short... if you have replicas attached it is suggested that you set a lower
  833. # limit for maxmemory so that there is some free RAM on the system for replica
  834. # output buffers (but this is not needed if the policy is 'noeviction').
  835. #
  836. # maxmemory <bytes>
  838. # MAXMEMORY POLICY: how Redis will select what to remove when maxmemory
  839. # is reached. You can select one from the following behaviors:
  840. #
  841. # volatile-lru -> Evict using approximated LRU, only keys with an expire set.
  842. # allkeys-lru -> Evict any key using approximated LRU.
  843. # volatile-lfu -> Evict using approximated LFU, only keys with an expire set.
  844. # allkeys-lfu -> Evict any key using approximated LFU.
  845. # volatile-random -> Remove a random key having an expire set.
  846. # allkeys-random -> Remove a random key, any key.
  847. # volatile-ttl -> Remove the key with the nearest expire time (minor TTL)
  848. # noeviction -> Don't evict anything, just return an error on write operations.
  849. #
  850. # LRU means Least Recently Used
  851. # LFU means Least Frequently Used
  852. #
  853. # Both LRU, LFU and volatile-ttl are implemented using approximated
  854. # randomized algorithms.
  855. #
  856. # Note: with any of the above policies, Redis will return an error on write
  857. #       operations, when there are no suitable keys for eviction.
  858. #
  859. #       At the date of writing these commands are: set setnx setex append
  860. #       incr decr rpush lpush rpushx lpushx linsert lset rpoplpush sadd
  861. #       sinter sinterstore sunion sunionstore sdiff sdiffstore zadd zincrby
  862. #       zunionstore zinterstore hset hsetnx hmset hincrby incrby decrby
  863. #       getset mset msetnx exec sort
  864. #
  865. # The default is:
  866. #
  867. # maxmemory-policy noeviction
  869. # LRU, LFU and minimal TTL algorithms are not precise algorithms but approximated
  870. # algorithms (in order to save memory), so you can tune it for speed or
  871. # accuracy. For default Redis will check five keys and pick the one that was
  872. # used less recently, you can change the sample size using the following
  873. # configuration directive.
  874. #
  875. # The default of 5 produces good enough results. 10 Approximates very closely
  876. # true LRU but costs more CPU. 3 is faster but not very accurate.
  877. #
  878. # maxmemory-samples 5
  880. # Starting from Redis 5, by default a replica will ignore its maxmemory setting
  881. # (unless it is promoted to master after a failover or manually). It means
  882. # that the eviction of keys will be just handled by the master, sending the
  883. # DEL commands to the replica as keys evict in the master side.
  884. #
  885. # This behavior ensures that masters and replicas stay consistent, and is usually
  886. # what you want, however if your replica is writable, or you want the replica
  887. # to have a different memory setting, and you are sure all the writes performed
  888. # to the replica are idempotent, then you may change this default (but be sure
  889. # to understand what you are doing).
  890. #
  891. # Note that since the replica by default does not evict, it may end using more
  892. # memory than the one set via maxmemory (there are certain buffers that may
  893. # be larger on the replica, or data structures may sometimes take more memory
  894. # and so forth). So make sure you monitor your replicas and make sure they
  895. # have enough memory to never hit a real out-of-memory condition before the
  896. # master hits the configured maxmemory setting.
  897. #
  898. # replica-ignore-maxmemory yes
  900. # Redis reclaims expired keys in two ways: upon access when those keys are
  901. # found to be expired, and also in background, in what is called the
  902. # "active expire key". The key space is slowly and interactively scanned
  903. # looking for expired keys to reclaim, so that it is possible to free memory
  904. # of keys that are expired and will never be accessed again in a short time.
  905. #
  906. # The default effort of the expire cycle will try to avoid having more than
  907. # ten percent of expired keys still in memory, and will try to avoid consuming
  908. # more than 25% of total memory and to add latency to the system. However
  909. # it is possible to increase the expire "effort" that is normally set to
  910. # "1", to a greater value, up to the value "10". At its maximum value the
  911. # system will use more CPU, longer cycles (and technically may introduce
  912. # more latency), and will tollerate less already expired keys still present
  913. # in the system. It's a tradeoff betweeen memory, CPU and latecy.
  914. #
  915. # active-expire-effort 1
  917. ############################# LAZY FREEING ####################################
  919. # Redis has two primitives to delete keys. One is called DEL and is a blocking
  920. # deletion of the object. It means that the server stops processing new commands
  921. # in order to reclaim all the memory associated with an object in a synchronous
  922. # way. If the key deleted is associated with a small object, the time needed
  923. # in order to execute the DEL command is very small and comparable to most other
  924. # O(1) or O(log_N) commands in Redis. However if the key is associated with an
  925. # aggregated value containing millions of elements, the server can block for
  926. # a long time (even seconds) in order to complete the operation.
  927. #
  928. # For the above reasons Redis also offers non blocking deletion primitives
  929. # such as UNLINK (non blocking DEL) and the ASYNC option of FLUSHALL and
  930. # FLUSHDB commands, in order to reclaim memory in background. Those commands
  931. # are executed in constant time. Another thread will incrementally free the
  932. # object in the background as fast as possible.
  933. #
  934. # DEL, UNLINK and ASYNC option of FLUSHALL and FLUSHDB are user-controlled.
  935. # It's up to the design of the application to understand when it is a good
  936. # idea to use one or the other. However the Redis server sometimes has to
  937. # delete keys or flush the whole database as a side effect of other operations.
  938. # Specifically Redis deletes objects independently of a user call in the
  939. # following scenarios:
  940. #
  941. # 1) On eviction, because of the maxmemory and maxmemory policy configurations,
  942. #    in order to make room for new data, without going over the specified
  943. #    memory limit.
  944. # 2) Because of expire: when a key with an associated time to live (see the
  945. #    EXPIRE command) must be deleted from memory.
  946. # 3) Because of a side effect of a command that stores data on a key that may
  947. #    already exist. For example the RENAME command may delete the old key
  948. #    content when it is replaced with another one. Similarly SUNIONSTORE
  949. #    or SORT with STORE option may delete existing keys. The SET command
  950. #    itself removes any old content of the specified key in order to replace
  951. #    it with the specified string.
  952. # 4) During replication, when a replica performs a full resynchronization with
  953. #    its master, the content of the whole database is removed in order to
  954. #    load the RDB file just transferred.
  955. #
  956. # In all the above cases the default is to delete objects in a blocking way,
  957. # like if DEL was called. However you can configure each case specifically
  958. # in order to instead release memory in a non-blocking way like if UNLINK
  959. # was called, using the following configuration directives.
  961. lazyfree-lazy-eviction no
  962. lazyfree-lazy-expire no
  963. lazyfree-lazy-server-del no
  964. replica-lazy-flush no
  966. # It is also possible, for the case when to replace the user code DEL calls
  967. # with UNLINK calls is not easy, to modify the default behavior of the DEL
  968. # command to act exactly like UNLINK, using the following configuration
  969. # directive:
  971. lazyfree-lazy-user-del no
  973. ################################ THREADED I/O #################################
  975. # Redis is mostly single threaded, however there are certain threaded
  976. # operations such as UNLINK, slow I/O accesses and other things that are
  977. # performed on side threads.
  978. #
  979. # Now it is also possible to handle Redis clients socket reads and writes
  980. # in different I/O threads. Since especially writing is so slow, normally
  981. # Redis users use pipelining in order to speedup the Redis performances per
  982. # core, and spawn multiple instances in order to scale more. Using I/O
  983. # threads it is possible to easily speedup two times Redis without resorting
  984. # to pipelining nor sharding of the instance.
  985. #
  986. # By default threading is disabled, we suggest enabling it only in machines
  987. # that have at least 4 or more cores, leaving at least one spare core.
  988. # Using more than 8 threads is unlikely to help much. We also recommend using
  989. # threaded I/O only if you actually have performance problems, with Redis
  990. # instances being able to use a quite big percentage of CPU time, otherwise
  991. # there is no point in using this feature.
  992. #
  993. # So for instance if you have a four cores boxes, try to use 2 or 3 I/O
  994. # threads, if you have a 8 cores, try to use 6 threads. In order to
  995. # enable I/O threads use the following configuration directive:
  996. #
  997. # io-threads 4
  998. #
  999. # Setting io-threads to 1 will just use the main thread as usually.
  1000. # When I/O threads are enabled, we only use threads for writes, that is
  1001. # to thread the write(2) syscall and transfer the client buffers to the
  1002. # socket. However it is also possible to enable threading of reads and
  1003. # protocol parsing using the following configuration directive, by setting
  1004. # it to yes:
  1005. #
  1006. # io-threads-do-reads no
  1007. #
  1008. # Usually threading reads doesn't help much.
  1009. #
  1010. # NOTE 1: This configuration directive cannot be changed at runtime via
  1011. # CONFIG SET. Aso this feature currently does not work when SSL is
  1012. # enabled.
  1013. #
  1014. # NOTE 2: If you want to test the Redis speedup using redis-benchmark, make
  1015. # sure you also run the benchmark itself in threaded mode, using the
  1016. # --threads option to match the number of Redis theads, otherwise you'll not
  1017. # be able to notice the improvements.
  1019. ############################## APPEND ONLY MODE ###############################
  1021. # By default Redis asynchronously dumps the dataset on disk. This mode is
  1022. # good enough in many applications, but an issue with the Redis process or
  1023. # a power outage may result into a few minutes of writes lost (depending on
  1024. # the configured save points).
  1025. #
  1026. # The Append Only File is an alternative persistence mode that provides
  1027. # much better durability. For instance using the default data fsync policy
  1028. # (see later in the config file) Redis can lose just one second of writes in a
  1029. # dramatic event like a server power outage, or a single write if something
  1030. # wrong with the Redis process itself happens, but the operating system is
  1031. # still running correctly.
  1032. #
  1033. # AOF and RDB persistence can be enabled at the same time without problems.
  1034. # If the AOF is enabled on startup Redis will load the AOF, that is the file
  1035. # with the better durability guarantees.
  1036. #
  1037. # Please check http://redis.io/topics/persistence for more information.
  1039. appendonly no
  1041. # The name of the append only file (default: "appendonly.aof")
  1043. appendfilename "appendonly.aof"
  1045. # The fsync() call tells the Operating System to actually write data on disk
  1046. # instead of waiting for more data in the output buffer. Some OS will really flush
  1047. # data on disk, some other OS will just try to do it ASAP.
  1048. #
  1049. # Redis supports three different modes:
  1050. #
  1051. # no: don't fsync, just let the OS flush the data when it wants. Faster.
  1052. # always: fsync after every write to the append only log. Slow, Safest.
  1053. # everysec: fsync only one time every second. Compromise.
  1054. #
  1055. # The default is "everysec", as that's usually the right compromise between
  1056. # speed and data safety. It's up to you to understand if you can relax this to
  1057. # "no" that will let the operating system flush the output buffer when
  1058. # it wants, for better performances (but if you can live with the idea of
  1059. # some data loss consider the default persistence mode that's snapshotting),
  1060. # or on the contrary, use "always" that's very slow but a bit safer than
  1061. # everysec.
  1062. #
  1063. # More details please check the following article:
  1064. # http://antirez.com/post/redis-persistence-demystified.html
  1065. #
  1066. # If unsure, use "everysec".
  1068. # appendfsync always
  1069. appendfsync everysec
  1070. # appendfsync no
  1072. # When the AOF fsync policy is set to always or everysec, and a background
  1073. # saving process (a background save or AOF log background rewriting) is
  1074. # performing a lot of I/O against the disk, in some Linux configurations
  1075. # Redis may block too long on the fsync() call. Note that there is no fix for
  1076. # this currently, as even performing fsync in a different thread will block
  1077. # our synchronous write(2) call.
  1078. #
  1079. # In order to mitigate this problem it's possible to use the following option
  1080. # that will prevent fsync() from being called in the main process while a
  1081. # BGSAVE or BGREWRITEAOF is in progress.
  1082. #
  1083. # This means that while another child is saving, the durability of Redis is
  1084. # the same as "appendfsync none". In practical terms, this means that it is
  1085. # possible to lose up to 30 seconds of log in the worst scenario (with the
  1086. # default Linux settings).
  1087. #
  1088. # If you have latency problems turn this to "yes". Otherwise leave it as
  1089. # "no" that is the safest pick from the point of view of durability.
  1091. no-appendfsync-on-rewrite no
  1093. # Automatic rewrite of the append only file.
  1094. # Redis is able to automatically rewrite the log file implicitly calling
  1095. # BGREWRITEAOF when the AOF log size grows by the specified percentage.
  1096. #
  1097. # This is how it works: Redis remembers the size of the AOF file after the
  1098. # latest rewrite (if no rewrite has happened since the restart, the size of
  1099. # the AOF at startup is used).
  1100. #
  1101. # This base size is compared to the current size. If the current size is
  1102. # bigger than the specified percentage, the rewrite is triggered. Also
  1103. # you need to specify a minimal size for the AOF file to be rewritten, this
  1104. # is useful to avoid rewriting the AOF file even if the percentage increase
  1105. # is reached but it is still pretty small.
  1106. #
  1107. # Specify a percentage of zero in order to disable the automatic AOF
  1108. # rewrite feature.
  1110. auto-aof-rewrite-percentage 100
  1111. auto-aof-rewrite-min-size 64mb
  1113. # An AOF file may be found to be truncated at the end during the Redis
  1114. # startup process, when the AOF data gets loaded back into memory.
  1115. # This may happen when the system where Redis is running
  1116. # crashes, especially when an ext4 filesystem is mounted without the
  1117. # data=ordered option (however this can't happen when Redis itself
  1118. # crashes or aborts but the operating system still works correctly).
  1119. #
  1120. # Redis can either exit with an error when this happens, or load as much
  1121. # data as possible (the default now) and start if the AOF file is found
  1122. # to be truncated at the end. The following option controls this behavior.
  1123. #
  1124. # If aof-load-truncated is set to yes, a truncated AOF file is loaded and
  1125. # the Redis server starts emitting a log to inform the user of the event.
  1126. # Otherwise if the option is set to no, the server aborts with an error
  1127. # and refuses to start. When the option is set to no, the user requires
  1128. # to fix the AOF file using the "redis-check-aof" utility before to restart
  1129. # the server.
  1130. #
  1131. # Note that if the AOF file will be found to be corrupted in the middle
  1132. # the server will still exit with an error. This option only applies when
  1133. # Redis will try to read more data from the AOF file but not enough bytes
  1134. # will be found.
  1135. aof-load-truncated yes
  1137. # When rewriting the AOF file, Redis is able to use an RDB preamble in the
  1138. # AOF file for faster rewrites and recoveries. When this option is turned
  1139. # on the rewritten AOF file is composed of two different stanzas:
  1140. #
  1141. #   [RDB file][AOF tail]
  1142. #
  1143. # When loading Redis recognizes that the AOF file starts with the "REDIS"
  1144. # string and loads the prefixed RDB file, and continues loading the AOF
  1145. # tail.
  1146. aof-use-rdb-preamble yes
  1148. ################################ LUA SCRIPTING  ###############################
  1150. # Max execution time of a Lua script in milliseconds.
  1151. #
  1152. # If the maximum execution time is reached Redis will log that a script is
  1153. # still in execution after the maximum allowed time and will start to
  1154. # reply to queries with an error.
  1155. #
  1156. # When a long running script exceeds the maximum execution time only the
  1157. # SCRIPT KILL and SHUTDOWN NOSAVE commands are available. The first can be
  1158. # used to stop a script that did not yet called write commands. The second
  1159. # is the only way to shut down the server in the case a write command was
  1160. # already issued by the script but the user doesn't want to wait for the natural
  1161. # termination of the script.
  1162. #
  1163. # Set it to 0 or a negative value for unlimited execution without warnings.
  1164. lua-time-limit 5000
  1166. ################################ REDIS CLUSTER  ###############################
  1168. # Normal Redis instances can't be part of a Redis Cluster; only nodes that are
  1169. # started as cluster nodes can. In order to start a Redis instance as a
  1170. # cluster node enable the cluster support uncommenting the following:
  1171. #
  1172. # cluster-enabled yes
  1174. # Every cluster node has a cluster configuration file. This file is not
  1175. # intended to be edited by hand. It is created and updated by Redis nodes.
  1176. # Every Redis Cluster node requires a different cluster configuration file.
  1177. # Make sure that instances running in the same system do not have
  1178. # overlapping cluster configuration file names.
  1179. #
  1180. # cluster-config-file nodes-6379.conf
  1182. # Cluster node timeout is the amount of milliseconds a node must be unreachable
  1183. # for it to be considered in failure state.
  1184. # Most other internal time limits are multiple of the node timeout.
  1185. #
  1186. # cluster-node-timeout 15000
  1188. # A replica of a failing master will avoid to start a failover if its data
  1189. # looks too old.
  1190. #
  1191. # There is no simple way for a replica to actually have an exact measure of
  1192. # its "data age", so the following two checks are performed:
  1193. #
  1194. # 1) If there are multiple replicas able to failover, they exchange messages
  1195. #    in order to try to give an advantage to the replica with the best
  1196. #    replication offset (more data from the master processed).
  1197. #    Replicas will try to get their rank by offset, and apply to the start
  1198. #    of the failover a delay proportional to their rank.
  1199. #
  1200. # 2) Every single replica computes the time of the last interaction with
  1201. #    its master. This can be the last ping or command received (if the master
  1202. #    is still in the "connected" state), or the time that elapsed since the
  1203. #    disconnection with the master (if the replication link is currently down).
  1204. #    If the last interaction is too old, the replica will not try to failover
  1205. #    at all.
  1206. #
  1207. # The point "2" can be tuned by user. Specifically a replica will not perform
  1208. # the failover if, since the last interaction with the master, the time
  1209. # elapsed is greater than:
  1210. #
  1211. #   (node-timeout * replica-validity-factor) + repl-ping-replica-period
  1212. #
  1213. # So for example if node-timeout is 30 seconds, and the replica-validity-factor
  1214. # is 10, and assuming a default repl-ping-replica-period of 10 seconds, the
  1215. # replica will not try to failover if it was not able to talk with the master
  1216. # for longer than 310 seconds.
  1217. #
  1218. # A large replica-validity-factor may allow replicas with too old data to failover
  1219. # a master, while a too small value may prevent the cluster from being able to
  1220. # elect a replica at all.
  1221. #
  1222. # For maximum availability, it is possible to set the replica-validity-factor
  1223. # to a value of 0, which means, that replicas will always try to failover the
  1224. # master regardless of the last time they interacted with the master.
  1225. # (However they'll always try to apply a delay proportional to their
  1226. # offset rank).
  1227. #
  1228. # Zero is the only value able to guarantee that when all the partitions heal
  1229. # the cluster will always be able to continue.
  1230. #
  1231. # cluster-replica-validity-factor 10
  1233. # Cluster replicas are able to migrate to orphaned masters, that are masters
  1234. # that are left without working replicas. This improves the cluster ability
  1235. # to resist to failures as otherwise an orphaned master can't be failed over
  1236. # in case of failure if it has no working replicas.
  1237. #
  1238. # Replicas migrate to orphaned masters only if there are still at least a
  1239. # given number of other working replicas for their old master. This number
  1240. # is the "migration barrier". A migration barrier of 1 means that a replica
  1241. # will migrate only if there is at least 1 other working replica for its master
  1242. # and so forth. It usually reflects the number of replicas you want for every
  1243. # master in your cluster.
  1244. #
  1245. # Default is 1 (replicas migrate only if their masters remain with at least
  1246. # one replica). To disable migration just set it to a very large value.
  1247. # A value of 0 can be set but is useful only for debugging and dangerous
  1248. # in production.
  1249. #
  1250. # cluster-migration-barrier 1
  1252. # By default Redis Cluster nodes stop accepting queries if they detect there
  1253. # is at least an hash slot uncovered (no available node is serving it).
  1254. # This way if the cluster is partially down (for example a range of hash slots
  1255. # are no longer covered) all the cluster becomes, eventually, unavailable.
  1256. # It automatically returns available as soon as all the slots are covered again.
  1257. #
  1258. # However sometimes you want the subset of the cluster which is working,
  1259. # to continue to accept queries for the part of the key space that is still
  1260. # covered. In order to do so, just set the cluster-require-full-coverage
  1261. # option to no.
  1262. #
  1263. # cluster-require-full-coverage yes
  1265. # This option, when set to yes, prevents replicas from trying to failover its
  1266. # master during master failures. However the master can still perform a
  1267. # manual failover, if forced to do so.
  1268. #
  1269. # This is useful in different scenarios, especially in the case of multiple
  1270. # data center operations, where we want one side to never be promoted if not
  1271. # in the case of a total DC failure.
  1272. #
  1273. # cluster-replica-no-failover no
  1275. # This option, when set to yes, allows nodes to serve read traffic while the
  1276. # the cluster is in a down state, as long as it believes it owns the slots. 
  1277. #
  1278. # This is useful for two cases.  The first case is for when an application 
  1279. # doesn't require consistency of data during node failures or network partitions.
  1280. # One example of this is a cache, where as long as the node has the data it
  1281. # should be able to serve it. 
  1282. #
  1283. # The second use case is for configurations that don't meet the recommended  
  1284. # three shards but want to enable cluster mode and scale later. A 
  1285. # master outage in a 1 or 2 shard configuration causes a read/write outage to the
  1286. # entire cluster without this option set, with it set there is only a write outage.
  1287. # Without a quorum of masters, slot ownership will not change automatically. 
  1288. #
  1289. # cluster-allow-reads-when-down no
  1291. # In order to setup your cluster make sure to read the documentation
  1292. # available at http://redis.io web site.
  1294. ########################## CLUSTER DOCKER/NAT support  ########################
  1296. # In certain deployments, Redis Cluster nodes address discovery fails, because
  1297. # addresses are NAT-ted or because ports are forwarded (the typical case is
  1298. # Docker and other containers).
  1299. #
  1300. # In order to make Redis Cluster working in such environments, a static
  1301. # configuration where each node knows its public address is needed. The
  1302. # following two options are used for this scope, and are:
  1303. #
  1304. # * cluster-announce-ip
  1305. # * cluster-announce-port
  1306. # * cluster-announce-bus-port
  1307. #
  1308. # Each instruct the node about its address, client port, and cluster message
  1309. # bus port. The information is then published in the header of the bus packets
  1310. # so that other nodes will be able to correctly map the address of the node
  1311. # publishing the information.
  1312. #
  1313. # If the above options are not used, the normal Redis Cluster auto-detection
  1314. # will be used instead.
  1315. #
  1316. # Note that when remapped, the bus port may not be at the fixed offset of
  1317. # clients port + 10000, so you can specify any port and bus-port depending
  1318. # on how they get remapped. If the bus-port is not set, a fixed offset of
  1319. # 10000 will be used as usually.
  1320. #
  1321. # Example:
  1322. #
  1323. # cluster-announce-ip 10.1.1.5
  1324. # cluster-announce-port 6379
  1325. # cluster-announce-bus-port 6380
  1327. ################################## SLOW LOG ###################################
  1329. # The Redis Slow Log is a system to log queries that exceeded a specified
  1330. # execution time. The execution time does not include the I/O operations
  1331. # like talking with the client, sending the reply and so forth,
  1332. # but just the time needed to actually execute the command (this is the only
  1333. # stage of command execution where the thread is blocked and can not serve
  1334. # other requests in the meantime).
  1335. #
  1336. # You can configure the slow log with two parameters: one tells Redis
  1337. # what is the execution time, in microseconds, to exceed in order for the
  1338. # command to get logged, and the other parameter is the length of the
  1339. # slow log. When a new command is logged the oldest one is removed from the
  1340. # queue of logged commands.
  1342. # The following time is expressed in microseconds, so 1000000 is equivalent
  1343. # to one second. Note that a negative number disables the slow log, while
  1344. # a value of zero forces the logging of every command.
  1345. slowlog-log-slower-than 10000
  1347. # There is no limit to this length. Just be aware that it will consume memory.
  1348. # You can reclaim memory used by the slow log with SLOWLOG RESET.
  1349. slowlog-max-len 128
  1351. ################################ LATENCY MONITOR ##############################
  1353. # The Redis latency monitoring subsystem samples different operations
  1354. # at runtime in order to collect data related to possible sources of
  1355. # latency of a Redis instance.
  1356. #
  1357. # Via the LATENCY command this information is available to the user that can
  1358. # print graphs and obtain reports.
  1359. #
  1360. # The system only logs operations that were performed in a time equal or
  1361. # greater than the amount of milliseconds specified via the
  1362. # latency-monitor-threshold configuration directive. When its value is set
  1363. # to zero, the latency monitor is turned off.
  1364. #
  1365. # By default latency monitoring is disabled since it is mostly not needed
  1366. # if you don't have latency issues, and collecting data has a performance
  1367. # impact, that while very small, can be measured under big load. Latency
  1368. # monitoring can easily be enabled at runtime using the command
  1369. # "CONFIG SET latency-monitor-threshold <milliseconds>" if needed.
  1370. latency-monitor-threshold 0
  1372. ############################# EVENT NOTIFICATION ##############################
  1374. # Redis can notify Pub/Sub clients about events happening in the key space.
  1375. # This feature is documented at http://redis.io/topics/notifications
  1376. #
  1377. # For instance if keyspace events notification is enabled, and a client
  1378. # performs a DEL operation on key "foo" stored in the Database 0, two
  1379. # messages will be published via Pub/Sub:
  1380. #
  1381. # PUBLISH __keyspace@0__:foo del
  1382. # PUBLISH __keyevent@0__:del foo
  1383. #
  1384. # It is possible to select the events that Redis will notify among a set
  1385. # of classes. Every class is identified by a single character:
  1386. #
  1387. #  K     Keyspace events, published with __keyspace@<db>__ prefix.
  1388. #  E     Keyevent events, published with __keyevent@<db>__ prefix.
  1389. #  g     Generic commands (non-type specific) like DEL, EXPIRE, RENAME, ...
  1390. #  $     String commands
  1391. #  l     List commands
  1392. #  s     Set commands
  1393. #  h     Hash commands
  1394. #  z     Sorted set commands
  1395. #  x     Expired events (events generated every time a key expires)
  1396. #  e     Evicted events (events generated when a key is evicted for maxmemory)
  1397. #  t     Stream commands
  1398. #  m     Key-miss events (Note: It is not included in the 'A' class)
  1399. #  A     Alias for g$lshzxet, so that the "AKE" string means all the events
  1400. #        (Except key-miss events which are excluded from 'A' due to their
  1401. #         unique nature).
  1402. #
  1403. #  The "notify-keyspace-events" takes as argument a string that is composed
  1404. #  of zero or multiple characters. The empty string means that notifications
  1405. #  are disabled.
  1406. #
  1407. #  Example: to enable list and generic events, from the point of view of the
  1408. #           event name, use:
  1409. #
  1410. #  notify-keyspace-events Elg
  1411. #
  1412. #  Example 2: to get the stream of the expired keys subscribing to channel
  1413. #             name __keyevent@0__:expired use:
  1414. #
  1415. #  notify-keyspace-events Ex
  1416. #
  1417. #  By default all notifications are disabled because most users don't need
  1418. #  this feature and the feature has some overhead. Note that if you don't
  1419. #  specify at least one of K or E, no events will be delivered.
  1420. notify-keyspace-events ""
  1422. ############################### GOPHER SERVER #################################
  1424. # Redis contains an implementation of the Gopher protocol, as specified in
  1425. # the RFC 1436 (https://www.ietf.org/rfc/rfc1436.txt).
  1426. #
  1427. # The Gopher protocol was very popular in the late '90s. It is an alternative
  1428. # to the web, and the implementation both server and client side is so simple
  1429. # that the Redis server has just 100 lines of code in order to implement this
  1430. # support.
  1431. #
  1432. # What do you do with Gopher nowadays? Well Gopher never *really* died, and
  1433. # lately there is a movement in order for the Gopher more hierarchical content
  1434. # composed of just plain text documents to be resurrected. Some want a simpler
  1435. # internet, others believe that the mainstream internet became too much
  1436. # controlled, and it's cool to create an alternative space for people that
  1437. # want a bit of fresh air.
  1438. #
  1439. # Anyway for the 10nth birthday of the Redis, we gave it the Gopher protocol
  1440. # as a gift.
  1441. #
  1442. # --- HOW IT WORKS? ---
  1443. #
  1444. # The Redis Gopher support uses the inline protocol of Redis, and specifically
  1445. # two kind of inline requests that were anyway illegal: an empty request
  1446. # or any request that starts with "/" (there are no Redis commands starting
  1447. # with such a slash). Normal RESP2/RESP3 requests are completely out of the
  1448. # path of the Gopher protocol implementation and are served as usually as well.
  1449. #
  1450. # If you open a connection to Redis when Gopher is enabled and send it
  1451. # a string like "/foo", if there is a key named "/foo" it is served via the
  1452. # Gopher protocol.
  1453. #
  1454. # In order to create a real Gopher "hole" (the name of a Gopher site in Gopher
  1455. # talking), you likely need a script like the following:
  1456. #
  1457. #   https://github.com/antirez/gopher2redis
  1458. #
  1459. # --- SECURITY WARNING ---
  1460. #
  1461. # If you plan to put Redis on the internet in a publicly accessible address
  1462. # to server Gopher pages MAKE SURE TO SET A PASSWORD to the instance.
  1463. # Once a password is set:
  1464. #
  1465. #   1. The Gopher server (when enabled, not by default) will still serve
  1466. #      content via Gopher.
  1467. #   2. However other commands cannot be called before the client will
  1468. #      authenticate.
  1469. #
  1470. # So use the 'requirepass' option to protect your instance.
  1471. #
  1472. # To enable Gopher support uncomment the following line and set
  1473. # the option from no (the default) to yes.
  1474. #
  1475. # gopher-enabled no
  1477. ############################### ADVANCED CONFIG ###############################
  1479. # Hashes are encoded using a memory efficient data structure when they have a
  1480. # small number of entries, and the biggest entry does not exceed a given
  1481. # threshold. These thresholds can be configured using the following directives.
  1482. hash-max-ziplist-entries 512
  1483. hash-max-ziplist-value 64
  1485. # Lists are also encoded in a special way to save a lot of space.
  1486. # The number of entries allowed per internal list node can be specified
  1487. # as a fixed maximum size or a maximum number of elements.
  1488. # For a fixed maximum size, use -5 through -1, meaning:
  1489. # -5: max size: 64 Kb  <-- not recommended for normal workloads
  1490. # -4: max size: 32 Kb  <-- not recommended
  1491. # -3: max size: 16 Kb  <-- probably not recommended
  1492. # -2: max size: 8 Kb   <-- good
  1493. # -1: max size: 4 Kb   <-- good
  1494. # Positive numbers mean store up to _exactly_ that number of elements
  1495. # per list node.
  1496. # The highest performing option is usually -2 (8 Kb size) or -1 (4 Kb size),
  1497. # but if your use case is unique, adjust the settings as necessary.
  1498. list-max-ziplist-size -2
  1500. # Lists may also be compressed.
  1501. # Compress depth is the number of quicklist ziplist nodes from *each* side of
  1502. # the list to *exclude* from compression.  The head and tail of the list
  1503. # are always uncompressed for fast push/pop operations.  Settings are:
  1504. # 0: disable all list compression
  1505. # 1: depth 1 means "don't start compressing until after 1 node into the list,
  1506. #    going from either the head or tail"
  1507. #    So: [head]->node->node->...->node->[tail]
  1508. #    [head], [tail] will always be uncompressed; inner nodes will compress.
  1509. # 2: [head]->[next]->node->node->...->node->[prev]->[tail]
  1510. #    2 here means: don't compress head or head->next or tail->prev or tail,
  1511. #    but compress all nodes between them.
  1512. # 3: [head]->[next]->[next]->node->node->...->node->[prev]->[prev]->[tail]
  1513. # etc.
  1514. list-compress-depth 0
  1516. # Sets have a special encoding in just one case: when a set is composed
  1517. # of just strings that happen to be integers in radix 10 in the range
  1518. # of 64 bit signed integers.
  1519. # The following configuration setting sets the limit in the size of the
  1520. # set in order to use this special memory saving encoding.
  1521. set-max-intset-entries 512
  1523. # Similarly to hashes and lists, sorted sets are also specially encoded in
  1524. # order to save a lot of space. This encoding is only used when the length and
  1525. # elements of a sorted set are below the following limits:
  1526. zset-max-ziplist-entries 128
  1527. zset-max-ziplist-value 64
  1529. # HyperLogLog sparse representation bytes limit. The limit includes the
  1530. # 16 bytes header. When an HyperLogLog using the sparse representation crosses
  1531. # this limit, it is converted into the dense representation.
  1532. #
  1533. # A value greater than 16000 is totally useless, since at that point the
  1534. # dense representation is more memory efficient.
  1535. #
  1536. # The suggested value is ~ 3000 in order to have the benefits of
  1537. # the space efficient encoding without slowing down too much PFADD,
  1538. # which is O(N) with the sparse encoding. The value can be raised to
  1539. # ~ 10000 when CPU is not a concern, but space is, and the data set is
  1540. # composed of many HyperLogLogs with cardinality in the 0 - 15000 range.
  1541. hll-sparse-max-bytes 3000
  1543. # Streams macro node max size / items. The stream data structure is a radix
  1544. # tree of big nodes that encode multiple items inside. Using this configuration
  1545. # it is possible to configure how big a single node can be in bytes, and the
  1546. # maximum number of items it may contain before switching to a new node when
  1547. # appending new stream entries. If any of the following settings are set to
  1548. # zero, the limit is ignored, so for instance it is possible to set just a
  1549. # max entires limit by setting max-bytes to 0 and max-entries to the desired
  1550. # value.
  1551. stream-node-max-bytes 4096
  1552. stream-node-max-entries 100
  1554. # Active rehashing uses 1 millisecond every 100 milliseconds of CPU time in
  1555. # order to help rehashing the main Redis hash table (the one mapping top-level
  1556. # keys to values). The hash table implementation Redis uses (see dict.c)
  1557. # performs a lazy rehashing: the more operation you run into a hash table
  1558. # that is rehashing, the more rehashing "steps" are performed, so if the
  1559. # server is idle the rehashing is never complete and some more memory is used
  1560. # by the hash table.
  1561. #
  1562. # The default is to use this millisecond 10 times every second in order to
  1563. # actively rehash the main dictionaries, freeing memory when possible.
  1564. #
  1565. # If unsure:
  1566. # use "activerehashing no" if you have hard latency requirements and it is
  1567. # not a good thing in your environment that Redis can reply from time to time
  1568. # to queries with 2 milliseconds delay.
  1569. #
  1570. # use "activerehashing yes" if you don't have such hard requirements but
  1571. # want to free memory asap when possible.
  1572. activerehashing yes
  1574. # The client output buffer limits can be used to force disconnection of clients
  1575. # that are not reading data from the server fast enough for some reason (a
  1576. # common reason is that a Pub/Sub client can't consume messages as fast as the
  1577. # publisher can produce them).
  1578. #
  1579. # The limit can be set differently for the three different classes of clients:
  1580. #
  1581. # normal -> normal clients including MONITOR clients
  1582. # replica  -> replica clients
  1583. # pubsub -> clients subscribed to at least one pubsub channel or pattern
  1584. #
  1585. # The syntax of every client-output-buffer-limit directive is the following:
  1586. #
  1587. # client-output-buffer-limit <class> <hard limit> <soft limit> <soft seconds>
  1588. #
  1589. # A client is immediately disconnected once the hard limit is reached, or if
  1590. # the soft limit is reached and remains reached for the specified number of
  1591. # seconds (continuously).
  1592. # So for instance if the hard limit is 32 megabytes and the soft limit is
  1593. # 16 megabytes / 10 seconds, the client will get disconnected immediately
  1594. # if the size of the output buffers reach 32 megabytes, but will also get
  1595. # disconnected if the client reaches 16 megabytes and continuously overcomes
  1596. # the limit for 10 seconds.
  1597. #
  1598. # By default normal clients are not limited because they don't receive data
  1599. # without asking (in a push way), but just after a request, so only
  1600. # asynchronous clients may create a scenario where data is requested faster
  1601. # than it can read.
  1602. #
  1603. # Instead there is a default limit for pubsub and replica clients, since
  1604. # subscribers and replicas receive data in a push fashion.
  1605. #
  1606. # Both the hard or the soft limit can be disabled by setting them to zero.
  1607. client-output-buffer-limit normal 0 0 0
  1608. client-output-buffer-limit replica 256mb 64mb 60
  1609. client-output-buffer-limit pubsub 32mb 8mb 60
  1611. # Client query buffers accumulate new commands. They are limited to a fixed
  1612. # amount by default in order to avoid that a protocol desynchronization (for
  1613. # instance due to a bug in the client) will lead to unbound memory usage in
  1614. # the query buffer. However you can configure it here if you have very special
  1615. # needs, such us huge multi/exec requests or alike.
  1616. #
  1617. # client-query-buffer-limit 1gb
  1619. # In the Redis protocol, bulk requests, that are, elements representing single
  1620. # strings, are normally limited ot 512 mb. However you can change this limit
  1621. # here.
  1622. #
  1623. # proto-max-bulk-len 512mb
  1625. # Redis calls an internal function to perform many background tasks, like
  1626. # closing connections of clients in timeout, purging expired keys that are
  1627. # never requested, and so forth.
  1628. #
  1629. # Not all tasks are performed with the same frequency, but Redis checks for
  1630. # tasks to perform according to the specified "hz" value.
  1631. #
  1632. # By default "hz" is set to 10. Raising the value will use more CPU when
  1633. # Redis is idle, but at the same time will make Redis more responsive when
  1634. # there are many keys expiring at the same time, and timeouts may be
  1635. # handled with more precision.
  1636. #
  1637. # The range is between 1 and 500, however a value over 100 is usually not
  1638. # a good idea. Most users should use the default of 10 and raise this up to
  1639. # 100 only in environments where very low latency is required.
  1640. hz 10
  1642. # Normally it is useful to have an HZ value which is proportional to the
  1643. # number of clients connected. This is useful in order, for instance, to
  1644. # avoid too many clients are processed for each background task invocation
  1645. # in order to avoid latency spikes.
  1646. #
  1647. # Since the default HZ value by default is conservatively set to 10, Redis
  1648. # offers, and enables by default, the ability to use an adaptive HZ value
  1649. # which will temporary raise when there are many connected clients.
  1650. #
  1651. # When dynamic HZ is enabled, the actual configured HZ will be used
  1652. # as a baseline, but multiples of the configured HZ value will be actually
  1653. # used as needed once more clients are connected. In this way an idle
  1654. # instance will use very little CPU time while a busy instance will be
  1655. # more responsive.
  1656. dynamic-hz yes
  1658. # When a child rewrites the AOF file, if the following option is enabled
  1659. # the file will be fsync-ed every 32 MB of data generated. This is useful
  1660. # in order to commit the file to the disk more incrementally and avoid
  1661. # big latency spikes.
  1662. aof-rewrite-incremental-fsync yes
  1664. # When redis saves RDB file, if the following option is enabled
  1665. # the file will be fsync-ed every 32 MB of data generated. This is useful
  1666. # in order to commit the file to the disk more incrementally and avoid
  1667. # big latency spikes.
  1668. rdb-save-incremental-fsync yes
  1670. # Redis LFU eviction (see maxmemory setting) can be tuned. However it is a good
  1671. # idea to start with the default settings and only change them after investigating
  1672. # how to improve the performances and how the keys LFU change over time, which
  1673. # is possible to inspect via the OBJECT FREQ command.
  1674. #
  1675. # There are two tunable parameters in the Redis LFU implementation: the
  1676. # counter logarithm factor and the counter decay time. It is important to
  1677. # understand what the two parameters mean before changing them.
  1678. #
  1679. # The LFU counter is just 8 bits per key, it's maximum value is 255, so Redis
  1680. # uses a probabilistic increment with logarithmic behavior. Given the value
  1681. # of the old counter, when a key is accessed, the counter is incremented in
  1682. # this way:
  1683. #
  1684. # 1. A random number R between 0 and 1 is extracted.
  1685. # 2. A probability P is calculated as 1/(old_value*lfu_log_factor+1).
  1686. # 3. The counter is incremented only if R < P.
  1687. #
  1688. # The default lfu-log-factor is 10. This is a table of how the frequency
  1689. # counter changes with a different number of accesses with different
  1690. # logarithmic factors:
  1691. #
  1692. # +--------+------------+------------+------------+------------+------------+
  1693. # | factor | 100 hits   | 1000 hits  | 100K hits  | 1M hits    | 10M hits   |
  1694. # +--------+------------+------------+------------+------------+------------+
  1695. # | 0      | 104        | 255        | 255        | 255        | 255        |
  1696. # +--------+------------+------------+------------+------------+------------+
  1697. # | 1      | 18         | 49         | 255        | 255        | 255        |
  1698. # +--------+------------+------------+------------+------------+------------+
  1699. # | 10     | 10         | 18         | 142        | 255        | 255        |
  1700. # +--------+------------+------------+------------+------------+------------+
  1701. # | 100    | 8          | 11         | 49         | 143        | 255        |
  1702. # +--------+------------+------------+------------+------------+------------+
  1703. #
  1704. # NOTE: The above table was obtained by running the following commands:
  1705. #
  1706. #   redis-benchmark -n 1000000 incr foo
  1707. #   redis-cli object freq foo
  1708. #
  1709. # NOTE 2: The counter initial value is 5 in order to give new objects a chance
  1710. # to accumulate hits.
  1711. #
  1712. # The counter decay time is the time, in minutes, that must elapse in order
  1713. # for the key counter to be divided by two (or decremented if it has a value
  1714. # less <= 10).
  1715. #
  1716. # The default value for the lfu-decay-time is 1. A Special value of 0 means to
  1717. # decay the counter every time it happens to be scanned.
  1718. #
  1719. # lfu-log-factor 10
  1720. # lfu-decay-time 1
  1722. ########################### ACTIVE DEFRAGMENTATION #######################
  1723. #
  1724. # What is active defragmentation?
  1725. # -------------------------------
  1726. #
  1727. # Active (online) defragmentation allows a Redis server to compact the
  1728. # spaces left between small allocations and deallocations of data in memory,
  1729. # thus allowing to reclaim back memory.
  1730. #
  1731. # Fragmentation is a natural process that happens with every allocator (but
  1732. # less so with Jemalloc, fortunately) and certain workloads. Normally a server
  1733. # restart is needed in order to lower the fragmentation, or at least to flush
  1734. # away all the data and create it again. However thanks to this feature
  1735. # implemented by Oran Agra for Redis 4.0 this process can happen at runtime
  1736. # in an "hot" way, while the server is running.
  1737. #
  1738. # Basically when the fragmentation is over a certain level (see the
  1739. # configuration options below) Redis will start to create new copies of the
  1740. # values in contiguous memory regions by exploiting certain specific Jemalloc
  1741. # features (in order to understand if an allocation is causing fragmentation
  1742. # and to allocate it in a better place), and at the same time, will release the
  1743. # old copies of the data. This process, repeated incrementally for all the keys
  1744. # will cause the fragmentation to drop back to normal values.
  1745. #
  1746. # Important things to understand:
  1747. #
  1748. # 1. This feature is disabled by default, and only works if you compiled Redis
  1749. #    to use the copy of Jemalloc we ship with the source code of Redis.
  1750. #    This is the default with Linux builds.
  1751. #
  1752. # 2. You never need to enable this feature if you don't have fragmentation
  1753. #    issues.
  1754. #
  1755. # 3. Once you experience fragmentation, you can enable this feature when
  1756. #    needed with the command "CONFIG SET activedefrag yes".
  1757. #
  1758. # The configuration parameters are able to fine tune the behavior of the
  1759. # defragmentation process. If you are not sure about what they mean it is
  1760. # a good idea to leave the defaults untouched.
  1762. # Enabled active defragmentation
  1763. # activedefrag no
  1765. # Minimum amount of fragmentation waste to start active defrag
  1766. # active-defrag-ignore-bytes 100mb
  1768. # Minimum percentage of fragmentation to start active defrag
  1769. # active-defrag-threshold-lower 10
  1771. # Maximum percentage of fragmentation at which we use maximum effort
  1772. # active-defrag-threshold-upper 100
  1774. # Minimal effort for defrag in CPU percentage, to be used when the lower
  1775. # threshold is reached
  1776. # active-defrag-cycle-min 1
  1778. # Maximal effort for defrag in CPU percentage, to be used when the upper
  1779. # threshold is reached
  1780. # active-defrag-cycle-max 25
  1782. # Maximum number of set/hash/zset/list fields that will be processed from
  1783. # the main dictionary scan
  1784. # active-defrag-max-scan-fields 1000
  1786. # Jemalloc background thread for purging will be enabled by default
  1787. jemalloc-bg-thread yes
  1789. # It is possible to pin different threads and processes of Redis to specific
  1790. # CPUs in your system, in order to maximize the performances of the server.
  1791. # This is useful both in order to pin different Redis threads in different
  1792. # CPUs, but also in order to make sure that multiple Redis instances running
  1793. # in the same host will be pinned to different CPUs.
  1794. #
  1795. # Normally you can do this using the "taskset" command, however it is also
  1796. # possible to this via Redis configuration directly, both in Linux and FreeBSD.
  1797. #
  1798. # You can pin the server/IO threads, bio threads, aof rewrite child process, and
  1799. # the bgsave child process. The syntax to specify the cpu list is the same as
  1800. # the taskset command:
  1801. #
  1802. # Set redis server/io threads to cpu affinity 0,2,4,6:
  1803. # server_cpulist 0-7:2
  1804. #
  1805. # Set bio threads to cpu affinity 1,3:
  1806. # bio_cpulist 1,3
  1807. #
  1808. # Set aof rewrite child process to cpu affinity 8,9,10,11:
  1809. # aof_rewrite_cpulist 8-11
  1810. #
  1811. # Set bgsave child process to cpu affinity 1,10,11
  1812. # bgsave_cpulist 1,10-11