Eolisation de Redis

redis-slave.conf 36KB

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