Eolisation de Redis
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.

redis.conf 36KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498499500501502503504505506507508509510511512513514515516517518519520521522523524525526527528529530531532533534535536537538539540541542543544545546547548549550551552553554555556557558559560561562563564565566567568569570571572573574575576577578579580581582583584585586587588589590591592593594595596597598599600601602603604605606607608609610611612613614615616617618619620621622623624625626627628629630631632633634635636637638639640641642643644645646647648649650651652653654655656657658659660661662663664665666667668669670671672673674675676677678679680681682683684685686687688689690691692693694695696697698699700701702703704705706707708709710711712713714715716717718719720721722723724725726727728729730731732733734735736737738739740741742743744745746747748749750751752753754755756757758759760761762763764765766767768769770771772773774775776777778779780781782783784785786787788789790791792793794795796797798799800801802803804805806807808809810811812813814815816817818819820821822823824825826827828829830831832833834835836837838839840841842843844845
  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. ################################## NETWORK #####################################
  35. # By default, if no "bind" configuration directive is specified, Redis listens
  36. # for connections from all the network interfaces available on the server.
  37. # It is possible to listen to just one or multiple selected interfaces using
  38. # the "bind" configuration directive, followed by one or more IP addresses.
  39. #
  40. # Examples:
  41. #
  42. # bind 192.168.1.100 10.0.0.1
  43. # bind 127.0.0.1 ::1
  44. #
  45. # ~~~ WARNING ~~~ If the computer running Redis is directly exposed to the
  46. # internet, binding to all the interfaces is dangerous and will expose the
  47. # instance to everybody on the internet. So by default we uncomment the
  48. # following bind directive, that will force Redis to listen only into
  49. # the IPv4 lookback interface address (this means Redis will be able to
  50. # accept connections only from clients running into the same computer it
  51. # is running).
  52. #
  53. # IF YOU ARE SURE YOU WANT YOUR INSTANCE TO LISTEN TO ALL THE INTERFACES
  54. # JUST COMMENT THE FOLLOWING LINE.
  55. # ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  56. bind 0.0.0.0
  57. # Protected mode is a layer of security protection, in order to avoid that
  58. # Redis instances left open on the internet are accessed and exploited.
  59. #
  60. # When protected mode is on and if:
  61. #
  62. # 1) The server is not binding explicitly to a set of addresses using the
  63. # "bind" directive.
  64. # 2) No password is configured.
  65. #
  66. # The server only accepts connections from clients connecting from the
  67. # IPv4 and IPv6 loopback addresses 127.0.0.1 and ::1, and from Unix domain
  68. # sockets.
  69. #
  70. # By default protected mode is enabled. You should disable it only if
  71. # you are sure you want clients from other hosts to connect to Redis
  72. # even if no authentication is configured, nor a specific set of interfaces
  73. # are explicitly listed using the "bind" directive.
  74. protected-mode no
  75. # Accept connections on the specified port, default is 6379 (IANA #815344).
  76. # If port 0 is specified Redis will not listen on a TCP socket.
  77. port %%redisPort
  78. # TCP listen() backlog.
  79. #
  80. # In high requests-per-second environments you need an high backlog in order
  81. # to avoid slow clients connections issues. Note that the Linux kernel
  82. # will silently truncate it to the value of /proc/sys/net/core/somaxconn so
  83. # make sure to raise both the value of somaxconn and tcp_max_syn_backlog
  84. # in order to get the desired effect.
  85. tcp-backlog 511
  86. # Unix socket.
  87. #
  88. # Specify the path for the Unix socket that will be used to listen for
  89. # incoming connections. There is no default, so Redis will not listen
  90. # on a unix socket when not specified.
  91. #
  92. # unixsocket /var/run/redis/redis.sock
  93. # unixsocketperm 700
  94. # Close the connection after a client is idle for N seconds (0 to disable)
  95. timeout 0
  96. # TCP keepalive.
  97. #
  98. # If non-zero, use SO_KEEPALIVE to send TCP ACKs to clients in absence
  99. # of communication. This is useful for two reasons:
  100. #
  101. # 1) Detect dead peers.
  102. # 2) Take the connection alive from the point of view of network
  103. # equipment in the middle.
  104. #
  105. # On Linux, the specified value (in seconds) is the period used to send ACKs.
  106. # Note that to close the connection the double of the time is needed.
  107. # On other kernels the period depends on the kernel configuration.
  108. #
  109. # A reasonable value for this option is 300 seconds, which is the new
  110. # Redis default starting with Redis 3.2.1.
  111. tcp-keepalive %%redisTCPKeepAlive
  112. ################################# GENERAL #####################################
  113. # By default Redis does not run as a daemon. Use 'yes' if you need it.
  114. # Note that Redis will write a pid file in /var/run/redis.pid when daemonized.
  115. daemonize yes
  116. # If you run Redis from upstart or systemd, Redis can interact with your
  117. # supervision tree. Options:
  118. # supervised no - no supervision interaction
  119. # supervised upstart - signal upstart by putting Redis into SIGSTOP mode
  120. # supervised systemd - signal systemd by writing READY=1 to $NOTIFY_SOCKET
  121. # supervised auto - detect upstart or systemd method based on
  122. # UPSTART_JOB or NOTIFY_SOCKET environment variables
  123. # Note: these supervision methods only signal "process is ready."
  124. # They do not enable continuous liveness pings back to your supervisor.
  125. supervised systemd
  126. # If a pid file is specified, Redis writes it where specified at startup
  127. # and removes it at exit.
  128. #
  129. # When the server runs non daemonized, no pid file is created if none is
  130. # specified in the configuration. When the server is daemonized, the pid file
  131. # is used even if not specified, defaulting to "/var/run/redis.pid".
  132. #
  133. # Creating a pid file is best effort: if Redis is not able to create it
  134. # nothing bad happens, the server will start and run normally.
  135. pidfile /var/run/redis/redis-server.pid
  136. # Specify the server verbosity level.
  137. # This can be one of:
  138. # debug (a lot of information, useful for development/testing)
  139. # verbose (many rarely useful info, but not a mess like the debug level)
  140. # notice (moderately verbose, what you want in production probably)
  141. # warning (only very important / critical messages are logged)
  142. loglevel notice
  143. # Specify the log file name. Also the empty string can be used to force
  144. # Redis to log on the standard output. Note that if you use standard
  145. # output for logging but daemonize, logs will be sent to /dev/null
  146. logfile /var/log/redis/redis-server.log
  147. # To enable logging to the system logger, just set 'syslog-enabled' to yes,
  148. # and optionally update the other syslog parameters to suit your needs.
  149. # syslog-enabled no
  150. # Specify the syslog identity.
  151. # syslog-ident redis
  152. # Specify the syslog facility. Must be USER or between LOCAL0-LOCAL7.
  153. # syslog-facility local0
  154. # Set the number of databases. The default database is DB 0, you can select
  155. # a different one on a per-connection basis using SELECT <dbid> where
  156. # dbid is a number between 0 and 'databases'-1
  157. databases 16
  158. ################################ SNAPSHOTTING ################################
  159. #
  160. # Save the DB on disk:
  161. #
  162. # save <seconds> <changes>
  163. #
  164. # Will save the DB if both the given number of seconds and the given
  165. # number of write operations against the DB occurred.
  166. #
  167. # In the example below the behaviour will be to save:
  168. # after 900 sec (15 min) if at least 1 key changed
  169. # after 300 sec (5 min) if at least 10 keys changed
  170. # after 60 sec if at least 10000 keys changed
  171. #
  172. # Note: you can disable saving completely by commenting out all "save" lines.
  173. #
  174. # It is also possible to remove all the previously configured save
  175. # points by adding a save directive with a single empty string argument
  176. # like in the following example:
  177. #
  178. # save ""
  179. %if %%rdSaveDisable == 'oui'
  180. save ""
  181. %else
  182. save 900 1
  183. save 300 10
  184. save 60 10000
  185. %end if
  186. # By default Redis will stop accepting writes if RDB snapshots are enabled
  187. # (at least one save point) and the latest background save failed.
  188. # This will make the user aware (in a hard way) that data is not persisting
  189. # on disk properly, otherwise chances are that no one will notice and some
  190. # disaster will happen.
  191. #
  192. # If the background saving process will start working again Redis will
  193. # automatically allow writes again.
  194. #
  195. # However if you have setup your proper monitoring of the Redis server
  196. # and persistence, you may want to disable this feature so that Redis will
  197. # continue to work as usual even if there are problems with disk,
  198. # permissions, and so forth.
  199. stop-writes-on-bgsave-error yes
  200. # Compress string objects using LZF when dump .rdb databases?
  201. # For default that's set to 'yes' as it's almost always a win.
  202. # If you want to save some CPU in the saving child set it to 'no' but
  203. # the dataset will likely be bigger if you have compressible values or keys.
  204. rdbcompression yes
  205. # Since version 5 of RDB a CRC64 checksum is placed at the end of the file.
  206. # This makes the format more resistant to corruption but there is a performance
  207. # hit to pay (around 10%) when saving and loading RDB files, so you can disable it
  208. # for maximum performances.
  209. #
  210. # RDB files created with checksum disabled have a checksum of zero that will
  211. # tell the loading code to skip the check.
  212. rdbchecksum yes
  213. # The filename where to dump the DB
  214. dbfilename dump.rdb
  215. # The working directory.
  216. #
  217. # The DB will be written inside this directory, with the filename specified
  218. # above using the 'dbfilename' configuration directive.
  219. #
  220. # The Append Only File will also be created inside this directory.
  221. #
  222. # Note that you must specify a directory here, not a file name.
  223. dir /var/lib/redis
  224. ################################## SECURITY ###################################
  225. # Require clients to issue AUTH <PASSWORD> before processing any other
  226. # commands. This might be useful in environments in which you do not trust
  227. # others with access to the host running redis-server.
  228. #
  229. # This should stay commented out for backward compatibility and because most
  230. # people do not need auth (e.g. they run their own servers).
  231. #
  232. # Warning: since Redis is pretty fast an outside user can try up to
  233. # 150k passwords per second against a good box. This means that you should
  234. # use a very strong password otherwise it will be very easy to break.
  235. #
  236. #requirepass redisMasterPassword
  237. # Command renaming.
  238. #
  239. # It is possible to change the name of dangerous commands in a shared
  240. # environment. For instance the CONFIG command may be renamed into something
  241. # hard to guess so that it will still be available for internal-use tools
  242. # but not available for general clients.
  243. #
  244. # Example:
  245. #
  246. # rename-command CONFIG b840fc02d524045429941cc15f59e41cb7be6c52
  247. #
  248. # It is also possible to completely kill a command by renaming it into
  249. # an empty string:
  250. #
  251. # rename-command CONFIG ""
  252. #
  253. # Please note that changing the name of commands that are logged into the
  254. # AOF file or transmitted to slaves may cause problems.
  255. ################################### LIMITS ####################################
  256. # Set the max number of connected clients at the same time. By default
  257. # this limit is set to 10000 clients, however if the Redis server is not
  258. # able to configure the process file limit to allow for the specified limit
  259. # the max number of allowed clients is set to the current file limit
  260. # minus 32 (as Redis reserves a few file descriptors for internal uses).
  261. #
  262. # Once the limit is reached Redis will close all the new connections sending
  263. # an error 'max number of clients reached'.
  264. #
  265. maxclients %%redisMaxClients
  266. # Don't use more memory than the specified amount of bytes.
  267. # When the memory limit is reached Redis will try to remove keys
  268. # according to the eviction policy selected (see maxmemory-policy).
  269. #
  270. # If Redis can't remove keys according to the policy, or if the policy is
  271. # set to 'noeviction', Redis will start to reply with errors to commands
  272. # that would use more memory, like SET, LPUSH, and so on, and will continue
  273. # to reply to read-only commands like GET.
  274. #
  275. # This option is usually useful when using Redis as an LRU cache, or to set
  276. # a hard memory limit for an instance (using the 'noeviction' policy).
  277. #
  278. # WARNING: If you have slaves attached to an instance with maxmemory on,
  279. # the size of the output buffers needed to feed the slaves are subtracted
  280. # from the used memory count, so that network problems / resyncs will
  281. # not trigger a loop where keys are evicted, and in turn the output
  282. # buffer of slaves is full with DELs of keys evicted triggering the deletion
  283. # of more keys, and so forth until the database is completely emptied.
  284. #
  285. # In short... if you have slaves attached it is suggested that you set a lower
  286. # limit for maxmemory so that there is some free RAM on the system for slave
  287. # output buffers (but this is not needed if the policy is 'noeviction').
  288. #
  289. maxmemory %%{redisMaxMemory}mb
  290. # MAXMEMORY POLICY: how Redis will select what to remove when maxmemory
  291. # is reached. You can select among five behaviors:
  292. #
  293. # volatile-lru -> remove the key with an expire set using an LRU algorithm
  294. # allkeys-lru -> remove any key according to the LRU algorithm
  295. # volatile-random -> remove a random key with an expire set
  296. # allkeys-random -> remove a random key, any key
  297. # volatile-ttl -> remove the key with the nearest expire time (minor TTL)
  298. # noeviction -> don't expire at all, just return an error on write operations
  299. #
  300. # Note: with any of the above policies, Redis will return an error on write
  301. # operations, when there are no suitable keys for eviction.
  302. #
  303. # At the date of writing these commands are: set setnx setex append
  304. # incr decr rpush lpush rpushx lpushx linsert lset rpoplpush sadd
  305. # sinter sinterstore sunion sunionstore sdiff sdiffstore zadd zincrby
  306. # zunionstore zinterstore hset hsetnx hmset hincrby incrby decrby
  307. # getset mset msetnx exec sort
  308. #
  309. # The default is:
  310. #
  311. maxmemory-policy %%redisMemoryPolicy
  312. # LRU and minimal TTL algorithms are not precise algorithms but approximated
  313. # algorithms (in order to save memory), so you can tune it for speed or
  314. # accuracy. For default Redis will check five keys and pick the one that was
  315. # used less recently, you can change the sample size using the following
  316. # configuration directive.
  317. #
  318. # The default of 5 produces good enough results. 10 Approximates very closely
  319. # true LRU but costs a bit more CPU. 3 is very fast but not very accurate.
  320. #
  321. # maxmemory-samples 5
  322. ############################## APPEND ONLY MODE ###############################
  323. # By default Redis asynchronously dumps the dataset on disk. This mode is
  324. # good enough in many applications, but an issue with the Redis process or
  325. # a power outage may result into a few minutes of writes lost (depending on
  326. # the configured save points).
  327. #
  328. # The Append Only File is an alternative persistence mode that provides
  329. # much better durability. For instance using the default data fsync policy
  330. # (see later in the config file) Redis can lose just one second of writes in a
  331. # dramatic event like a server power outage, or a single write if something
  332. # wrong with the Redis process itself happens, but the operating system is
  333. # still running correctly.
  334. #
  335. # AOF and RDB persistence can be enabled at the same time without problems.
  336. # If the AOF is enabled on startup Redis will load the AOF, that is the file
  337. # with the better durability guarantees.
  338. #
  339. # Please check http://redis.io/topics/persistence for more information.
  340. %if %%rdAOFDisable == 'oui'
  341. appendonly no
  342. %else
  343. appendonly yes
  344. %end if
  345. # The name of the append only file (default: "appendonly.aof")
  346. appendfilename "appendonly.aof"
  347. # The fsync() call tells the Operating System to actually write data on disk
  348. # instead of waiting for more data in the output buffer. Some OS will really flush
  349. # data on disk, some other OS will just try to do it ASAP.
  350. #
  351. # Redis supports three different modes:
  352. #
  353. # no: don't fsync, just let the OS flush the data when it wants. Faster.
  354. # always: fsync after every write to the append only log. Slow, Safest.
  355. # everysec: fsync only one time every second. Compromise.
  356. #
  357. # The default is "everysec", as that's usually the right compromise between
  358. # speed and data safety. It's up to you to understand if you can relax this to
  359. # "no" that will let the operating system flush the output buffer when
  360. # it wants, for better performances (but if you can live with the idea of
  361. # some data loss consider the default persistence mode that's snapshotting),
  362. # or on the contrary, use "always" that's very slow but a bit safer than
  363. # everysec.
  364. #
  365. # More details please check the following article:
  366. # http://antirez.com/post/redis-persistence-demystified.html
  367. #
  368. # If unsure, use "everysec".
  369. # appendfsync always
  370. appendfsync everysec
  371. # appendfsync no
  372. # When the AOF fsync policy is set to always or everysec, and a background
  373. # saving process (a background save or AOF log background rewriting) is
  374. # performing a lot of I/O against the disk, in some Linux configurations
  375. # Redis may block too long on the fsync() call. Note that there is no fix for
  376. # this currently, as even performing fsync in a different thread will block
  377. # our synchronous write(2) call.
  378. #
  379. # In order to mitigate this problem it's possible to use the following option
  380. # that will prevent fsync() from being called in the main process while a
  381. # BGSAVE or BGREWRITEAOF is in progress.
  382. #
  383. # This means that while another child is saving, the durability of Redis is
  384. # the same as "appendfsync none". In practical terms, this means that it is
  385. # possible to lose up to 30 seconds of log in the worst scenario (with the
  386. # default Linux settings).
  387. #
  388. # If you have latency problems turn this to "yes". Otherwise leave it as
  389. # "no" that is the safest pick from the point of view of durability.
  390. no-appendfsync-on-rewrite no
  391. # Automatic rewrite of the append only file.
  392. # Redis is able to automatically rewrite the log file implicitly calling
  393. # BGREWRITEAOF when the AOF log size grows by the specified percentage.
  394. #
  395. # This is how it works: Redis remembers the size of the AOF file after the
  396. # latest rewrite (if no rewrite has happened since the restart, the size of
  397. # the AOF at startup is used).
  398. #
  399. # This base size is compared to the current size. If the current size is
  400. # bigger than the specified percentage, the rewrite is triggered. Also
  401. # you need to specify a minimal size for the AOF file to be rewritten, this
  402. # is useful to avoid rewriting the AOF file even if the percentage increase
  403. # is reached but it is still pretty small.
  404. #
  405. # Specify a percentage of zero in order to disable the automatic AOF
  406. # rewrite feature.
  407. auto-aof-rewrite-percentage 100
  408. auto-aof-rewrite-min-size 64mb
  409. # An AOF file may be found to be truncated at the end during the Redis
  410. # startup process, when the AOF data gets loaded back into memory.
  411. # This may happen when the system where Redis is running
  412. # crashes, especially when an ext4 filesystem is mounted without the
  413. # data=ordered option (however this can't happen when Redis itself
  414. # crashes or aborts but the operating system still works correctly).
  415. #
  416. # Redis can either exit with an error when this happens, or load as much
  417. # data as possible (the default now) and start if the AOF file is found
  418. # to be truncated at the end. The following option controls this behavior.
  419. #
  420. # If aof-load-truncated is set to yes, a truncated AOF file is loaded and
  421. # the Redis server starts emitting a log to inform the user of the event.
  422. # Otherwise if the option is set to no, the server aborts with an error
  423. # and refuses to start. When the option is set to no, the user requires
  424. # to fix the AOF file using the "redis-check-aof" utility before to restart
  425. # the server.
  426. #
  427. # Note that if the AOF file will be found to be corrupted in the middle
  428. # the server will still exit with an error. This option only applies when
  429. # Redis will try to read more data from the AOF file but not enough bytes
  430. # will be found.
  431. aof-load-truncated yes
  432. ################################ LUA SCRIPTING ###############################
  433. # Max execution time of a Lua script in milliseconds.
  434. #
  435. # If the maximum execution time is reached Redis will log that a script is
  436. # still in execution after the maximum allowed time and will start to
  437. # reply to queries with an error.
  438. #
  439. # When a long running script exceeds the maximum execution time only the
  440. # SCRIPT KILL and SHUTDOWN NOSAVE commands are available. The first can be
  441. # used to stop a script that did not yet called write commands. The second
  442. # is the only way to shut down the server in the case a write command was
  443. # already issued by the script but the user doesn't want to wait for the natural
  444. # termination of the script.
  445. #
  446. # Set it to 0 or a negative value for unlimited execution without warnings.
  447. lua-time-limit 5000
  448. %if %%getVar('redisMode','Local') == "Cluster"
  449. ################################ REDIS CLUSTER ###############################
  450. #
  451. # ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
  452. # WARNING EXPERIMENTAL: Redis Cluster is considered to be stable code, however
  453. # in order to mark it as "mature" we need to wait for a non trivial percentage
  454. # of users to deploy it in production.
  455. # ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
  456. #
  457. # Normal Redis instances can't be part of a Redis Cluster; only nodes that are
  458. # started as cluster nodes can. In order to start a Redis instance as a
  459. # cluster node enable the cluster support uncommenting the following:
  460. #
  461. cluster-enabled yes
  462. # Every cluster node has a cluster configuration file. This file is not
  463. # intended to be edited by hand. It is created and updated by Redis nodes.
  464. # Every Redis Cluster node requires a different cluster configuration file.
  465. # Make sure that instances running in the same system do not have
  466. # overlapping cluster configuration file names.
  467. #
  468. cluster-config-file nodes.conf
  469. # Cluster node timeout is the amount of milliseconds a node must be unreachable
  470. # for it to be considered in failure state.
  471. # Most other internal time limits are multiple of the node timeout.
  472. #
  473. cluster-node-timeout 15000
  474. # A slave of a failing master will avoid to start a failover if its data
  475. # looks too old.
  476. #
  477. # There is no simple way for a slave to actually have a exact measure of
  478. # its "data age", so the following two checks are performed:
  479. #
  480. # 1) If there are multiple slaves able to failover, they exchange messages
  481. # in order to try to give an advantage to the slave with the best
  482. # replication offset (more data from the master processed).
  483. # Slaves will try to get their rank by offset, and apply to the start
  484. # of the failover a delay proportional to their rank.
  485. #
  486. # 2) Every single slave computes the time of the last interaction with
  487. # its master. This can be the last ping or command received (if the master
  488. # is still in the "connected" state), or the time that elapsed since the
  489. # disconnection with the master (if the replication link is currently down).
  490. # If the last interaction is too old, the slave will not try to failover
  491. # at all.
  492. #
  493. # The point "2" can be tuned by user. Specifically a slave will not perform
  494. # the failover if, since the last interaction with the master, the time
  495. # elapsed is greater than:
  496. #
  497. # (node-timeout * slave-validity-factor) + repl-ping-slave-period
  498. #
  499. # So for example if node-timeout is 30 seconds, and the slave-validity-factor
  500. # is 10, and assuming a default repl-ping-slave-period of 10 seconds, the
  501. # slave will not try to failover if it was not able to talk with the master
  502. # for longer than 310 seconds.
  503. #
  504. # A large slave-validity-factor may allow slaves with too old data to failover
  505. # a master, while a too small value may prevent the cluster from being able to
  506. # elect a slave at all.
  507. #
  508. # For maximum availability, it is possible to set the slave-validity-factor
  509. # to a value of 0, which means, that slaves will always try to failover the
  510. # master regardless of the last time they interacted with the master.
  511. # (However they'll always try to apply a delay proportional to their
  512. # offset rank).
  513. #
  514. # Zero is the only value able to guarantee that when all the partitions heal
  515. # the cluster will always be able to continue.
  516. #
  517. cluster-slave-validity-factor 10
  518. # Cluster slaves are able to migrate to orphaned masters, that are masters
  519. # that are left without working slaves. This improves the cluster ability
  520. # to resist to failures as otherwise an orphaned master can't be failed over
  521. # in case of failure if it has no working slaves.
  522. #
  523. # Slaves migrate to orphaned masters only if there are still at least a
  524. # given number of other working slaves for their old master. This number
  525. # is the "migration barrier". A migration barrier of 1 means that a slave
  526. # will migrate only if there is at least 1 other working slave for its master
  527. # and so forth. It usually reflects the number of slaves you want for every
  528. # master in your cluster.
  529. #
  530. # Default is 1 (slaves migrate only if their masters remain with at least
  531. # one slave). To disable migration just set it to a very large value.
  532. # A value of 0 can be set but is useful only for debugging and dangerous
  533. # in production.
  534. #
  535. cluster-migration-barrier 1
  536. # By default Redis Cluster nodes stop accepting queries if they detect there
  537. # is at least an hash slot uncovered (no available node is serving it).
  538. # This way if the cluster is partially down (for example a range of hash slots
  539. # are no longer covered) all the cluster becomes, eventually, unavailable.
  540. # It automatically returns available as soon as all the slots are covered again.
  541. #
  542. # However sometimes you want the subset of the cluster which is working,
  543. # to continue to accept queries for the part of the key space that is still
  544. # covered. In order to do so, just set the cluster-require-full-coverage
  545. # option to no.
  546. #
  547. cluster-require-full-coverage yes
  548. # In order to setup your cluster make sure to read the documentation
  549. # available at http://redis.io web site.
  550. %end if
  551. ################################## SLOW LOG ###################################
  552. # The Redis Slow Log is a system to log queries that exceeded a specified
  553. # execution time. The execution time does not include the I/O operations
  554. # like talking with the client, sending the reply and so forth,
  555. # but just the time needed to actually execute the command (this is the only
  556. # stage of command execution where the thread is blocked and can not serve
  557. # other requests in the meantime).
  558. #
  559. # You can configure the slow log with two parameters: one tells Redis
  560. # what is the execution time, in microseconds, to exceed in order for the
  561. # command to get logged, and the other parameter is the length of the
  562. # slow log. When a new command is logged the oldest one is removed from the
  563. # queue of logged commands.
  564. # The following time is expressed in microseconds, so 1000000 is equivalent
  565. # to one second. Note that a negative number disables the slow log, while
  566. # a value of zero forces the logging of every command.
  567. slowlog-log-slower-than 10000
  568. # There is no limit to this length. Just be aware that it will consume memory.
  569. # You can reclaim memory used by the slow log with SLOWLOG RESET.
  570. slowlog-max-len 128
  571. ################################ LATENCY MONITOR ##############################
  572. # The Redis latency monitoring subsystem samples different operations
  573. # at runtime in order to collect data related to possible sources of
  574. # latency of a Redis instance.
  575. #
  576. # Via the LATENCY command this information is available to the user that can
  577. # print graphs and obtain reports.
  578. #
  579. # The system only logs operations that were performed in a time equal or
  580. # greater than the amount of milliseconds specified via the
  581. # latency-monitor-threshold configuration directive. When its value is set
  582. # to zero, the latency monitor is turned off.
  583. #
  584. # By default latency monitoring is disabled since it is mostly not needed
  585. # if you don't have latency issues, and collecting data has a performance
  586. # impact, that while very small, can be measured under big load. Latency
  587. # monitoring can easily be enabled at runtime using the command
  588. # "CONFIG SET latency-monitor-threshold <milliseconds>" if needed.
  589. latency-monitor-threshold 0
  590. ############################# EVENT NOTIFICATION ##############################
  591. # Redis can notify Pub/Sub clients about events happening in the key space.
  592. # This feature is documented at http://redis.io/topics/notifications
  593. #
  594. # For instance if keyspace events notification is enabled, and a client
  595. # performs a DEL operation on key "foo" stored in the Database 0, two
  596. # messages will be published via Pub/Sub:
  597. #
  598. # PUBLISH __keyspace@0__:foo del
  599. # PUBLISH __keyevent@0__:del foo
  600. #
  601. # It is possible to select the events that Redis will notify among a set
  602. # of classes. Every class is identified by a single character:
  603. #
  604. # K Keyspace events, published with __keyspace@<db>__ prefix.
  605. # E Keyevent events, published with __keyevent@<db>__ prefix.
  606. # g Generic commands (non-type specific) like DEL, EXPIRE, RENAME, ...
  607. # $ String commands
  608. # l List commands
  609. # s Set commands
  610. # h Hash commands
  611. # z Sorted set commands
  612. # x Expired events (events generated every time a key expires)
  613. # e Evicted events (events generated when a key is evicted for maxmemory)
  614. # A Alias for g$lshzxe, so that the "AKE" string means all the events.
  615. #
  616. # The "notify-keyspace-events" takes as argument a string that is composed
  617. # of zero or multiple characters. The empty string means that notifications
  618. # are disabled.
  619. #
  620. # Example: to enable list and generic events, from the point of view of the
  621. # event name, use:
  622. #
  623. # notify-keyspace-events Elg
  624. #
  625. # Example 2: to get the stream of the expired keys subscribing to channel
  626. # name __keyevent@0__:expired use:
  627. #
  628. # notify-keyspace-events Ex
  629. #
  630. # By default all notifications are disabled because most users don't need
  631. # this feature and the feature has some overhead. Note that if you don't
  632. # specify at least one of K or E, no events will be delivered.
  633. notify-keyspace-events ""
  634. ############################### ADVANCED CONFIG ###############################
  635. # Hashes are encoded using a memory efficient data structure when they have a
  636. # small number of entries, and the biggest entry does not exceed a given
  637. # threshold. These thresholds can be configured using the following directives.
  638. hash-max-ziplist-entries 512
  639. hash-max-ziplist-value 64
  640. # Lists are also encoded in a special way to save a lot of space.
  641. # The number of entries allowed per internal list node can be specified
  642. # as a fixed maximum size or a maximum number of elements.
  643. # For a fixed maximum size, use -5 through -1, meaning:
  644. # -5: max size: 64 Kb <-- not recommended for normal workloads
  645. # -4: max size: 32 Kb <-- not recommended
  646. # -3: max size: 16 Kb <-- probably not recommended
  647. # -2: max size: 8 Kb <-- good
  648. # -1: max size: 4 Kb <-- good
  649. # Positive numbers mean store up to _exactly_ that number of elements
  650. # per list node.
  651. # The highest performing option is usually -2 (8 Kb size) or -1 (4 Kb size),
  652. # but if your use case is unique, adjust the settings as necessary.
  653. list-max-ziplist-size -2
  654. # Lists may also be compressed.
  655. # Compress depth is the number of quicklist ziplist nodes from *each* side of
  656. # the list to *exclude* from compression. The head and tail of the list
  657. # are always uncompressed for fast push/pop operations. Settings are:
  658. # 0: disable all list compression
  659. # 1: depth 1 means "don't start compressing until after 1 node into the list,
  660. # going from either the head or tail"
  661. # So: [head]->node->node->...->node->[tail]
  662. # [head], [tail] will always be uncompressed; inner nodes will compress.
  663. # 2: [head]->[next]->node->node->...->node->[prev]->[tail]
  664. # 2 here means: don't compress head or head->next or tail->prev or tail,
  665. # but compress all nodes between them.
  666. # 3: [head]->[next]->[next]->node->node->...->node->[prev]->[prev]->[tail]
  667. # etc.
  668. list-compress-depth 0
  669. # Sets have a special encoding in just one case: when a set is composed
  670. # of just strings that happen to be integers in radix 10 in the range
  671. # of 64 bit signed integers.
  672. # The following configuration setting sets the limit in the size of the
  673. # set in order to use this special memory saving encoding.
  674. set-max-intset-entries 512
  675. # Similarly to hashes and lists, sorted sets are also specially encoded in
  676. # order to save a lot of space. This encoding is only used when the length and
  677. # elements of a sorted set are below the following limits:
  678. zset-max-ziplist-entries 128
  679. zset-max-ziplist-value 64
  680. # HyperLogLog sparse representation bytes limit. The limit includes the
  681. # 16 bytes header. When an HyperLogLog using the sparse representation crosses
  682. # this limit, it is converted into the dense representation.
  683. #
  684. # A value greater than 16000 is totally useless, since at that point the
  685. # dense representation is more memory efficient.
  686. #
  687. # The suggested value is ~ 3000 in order to have the benefits of
  688. # the space efficient encoding without slowing down too much PFADD,
  689. # which is O(N) with the sparse encoding. The value can be raised to
  690. # ~ 10000 when CPU is not a concern, but space is, and the data set is
  691. # composed of many HyperLogLogs with cardinality in the 0 - 15000 range.
  692. hll-sparse-max-bytes 3000
  693. # Active rehashing uses 1 millisecond every 100 milliseconds of CPU time in
  694. # order to help rehashing the main Redis hash table (the one mapping top-level
  695. # keys to values). The hash table implementation Redis uses (see dict.c)
  696. # performs a lazy rehashing: the more operation you run into a hash table
  697. # that is rehashing, the more rehashing "steps" are performed, so if the
  698. # server is idle the rehashing is never complete and some more memory is used
  699. # by the hash table.
  700. #
  701. # The default is to use this millisecond 10 times every second in order to
  702. # actively rehash the main dictionaries, freeing memory when possible.
  703. #
  704. # If unsure:
  705. # use "activerehashing no" if you have hard latency requirements and it is
  706. # not a good thing in your environment that Redis can reply from time to time
  707. # to queries with 2 milliseconds delay.
  708. #
  709. # use "activerehashing yes" if you don't have such hard requirements but
  710. # want to free memory asap when possible.
  711. activerehashing yes
  712. # The client output buffer limits can be used to force disconnection of clients
  713. # that are not reading data from the server fast enough for some reason (a
  714. # common reason is that a Pub/Sub client can't consume messages as fast as the
  715. # publisher can produce them).
  716. #
  717. # The limit can be set differently for the three different classes of clients:
  718. #
  719. # normal -> normal clients including MONITOR clients
  720. # slave -> slave clients
  721. # pubsub -> clients subscribed to at least one pubsub channel or pattern
  722. #
  723. # The syntax of every client-output-buffer-limit directive is the following:
  724. #
  725. # client-output-buffer-limit <class> <hard limit> <soft limit> <soft seconds>
  726. #
  727. # A client is immediately disconnected once the hard limit is reached, or if
  728. # the soft limit is reached and remains reached for the specified number of
  729. # seconds (continuously).
  730. # So for instance if the hard limit is 32 megabytes and the soft limit is
  731. # 16 megabytes / 10 seconds, the client will get disconnected immediately
  732. # if the size of the output buffers reach 32 megabytes, but will also get
  733. # disconnected if the client reaches 16 megabytes and continuously overcomes
  734. # the limit for 10 seconds.
  735. #
  736. # By default normal clients are not limited because they don't receive data
  737. # without asking (in a push way), but just after a request, so only
  738. # asynchronous clients may create a scenario where data is requested faster
  739. # than it can read.
  740. #
  741. # Instead there is a default limit for pubsub and slave clients, since
  742. # subscribers and slaves receive data in a push fashion.
  743. #
  744. # Both the hard or the soft limit can be disabled by setting them to zero.
  745. client-output-buffer-limit normal 0 0 0
  746. client-output-buffer-limit slave %%{rdCliOutBuffHardLimit}mb %%{rdCliOutBuffSoftLimit}mb 60
  747. client-output-buffer-limit pubsub 32mb 8mb 60
  748. # Redis calls an internal function to perform many background tasks, like
  749. # closing connections of clients in timeout, purging expired keys that are
  750. # never requested, and so forth.
  751. #
  752. # Not all tasks are performed with the same frequency, but Redis checks for
  753. # tasks to perform according to the specified "hz" value.
  754. #
  755. # By default "hz" is set to 10. Raising the value will use more CPU when
  756. # Redis is idle, but at the same time will make Redis more responsive when
  757. # there are many keys expiring at the same time, and timeouts may be
  758. # handled with more precision.
  759. #
  760. # The range is between 1 and 500, however a value over 100 is usually not
  761. # a good idea. Most users should use the default of 10 and raise this up to
  762. # 100 only in environments where very low latency is required.
  763. hz 10
  764. # When a child rewrites the AOF file, if the following option is enabled
  765. # the file will be fsync-ed every 32 MB of data generated. This is useful
  766. # in order to commit the file to the disk more incrementally and avoid
  767. # big latency spikes.
  768. aof-rewrite-incremental-fsync yes