You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

1319 lines
57 KiB

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