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 72KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498499500501502503504505506507508509510511512513514515516517518519520521522523524525526527528529530531532533534535536537538539540541542543544545546547548549550551552553554555556557558559560561562563564565566567568569570571572573574575576577578579580581582583584585586587588589590591592593594595596597598599600601602603604605606607608609610611612613614615616617618619620621622623624625626627628629630631632633634635636637638639640641642643644645646647648649650651652653654655656657658659660661662663664665666667668669670671672673674675676677678679680681682683684685686687688689690691692693694695696697698699700701702703704705706707708709710711712713714715716717718719720721722723724725726727728729730731732733734735736737738739740741742743744745746747748749750751752753754755756757758759760761762763764765766767768769770771772773774775776777778779780781782783784785786787788789790791792793794795796797798799800801802803804805806807808809810811812813814815816817818819820821822823824825826827828829830831832833834835836837838839840841842843844845846847848849850851852853854855856857858859860861862863864865866867868869870871872873874875876877878879880881882883884885886887888889890891892893894895896897898899900901902903904905906907908909910911912913914915916917918919920921922923924925926927928929930931932933934935936937938939940941942943944945946947948949950951952953954955956957958959960961962963964965966967968969970971972973974975976977978979980981982983984985986987988989990991992993994995996997998999100010011002100310041005100610071008100910101011101210131014101510161017101810191020102110221023102410251026102710281029103010311032103310341035103610371038103910401041104210431044104510461047104810491050105110521053105410551056105710581059106010611062106310641065106610671068106910701071107210731074107510761077107810791080108110821083108410851086108710881089109010911092109310941095109610971098109911001101110211031104110511061107110811091110111111121113111411151116111711181119112011211122112311241125112611271128112911301131113211331134113511361137113811391140114111421143114411451146114711481149115011511152115311541155115611571158115911601161116211631164116511661167116811691170117111721173117411751176117711781179118011811182118311841185118611871188118911901191119211931194119511961197119811991200120112021203120412051206120712081209121012111212121312141215121612171218121912201221122212231224122512261227122812291230123112321233123412351236123712381239124012411242124312441245124612471248124912501251125212531254125512561257125812591260126112621263126412651266126712681269127012711272127312741275127612771278127912801281128212831284128512861287128812891290129112921293129412951296129712981299130013011302130313041305130613071308130913101311131213131314131513161317131813191320132113221323132413251326132713281329133013311332133313341335133613371338133913401341134213431344134513461347134813491350135113521353135413551356135713581359136013611362136313641365136613671368136913701371137213731374137513761377137813791380138113821383138413851386138713881389139013911392139313941395139613971398139914001401140214031404140514061407140814091410141114121413141414151416141714181419142014211422142314241425142614271428142914301431143214331434143514361437143814391440144114421443144414451446144714481449145014511452145314541455145614571458145914601461146214631464146514661467146814691470147114721473147414751476147714781479148014811482148314841485148614871488148914901491149214931494149514961497149814991500150115021503150415051506150715081509151015111512151315141515151615171518151915201521152215231524152515261527152815291530153115321533153415351536153715381539154015411542154315441545154615471548154915501551155215531554155515561557155815591560156115621563156415651566156715681569157015711572157315741575157615771578157915801581158215831584158515861587158815891590159115921593159415951596159715981599160016011602
  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 loopback 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 yes
  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 900 1
  193. save 300 10
  194. save 60 10000
  195. # By default Redis will stop accepting writes if RDB snapshots are enabled
  196. # (at least one save point) and the latest background save failed.
  197. # This will make the user aware (in a hard way) that data is not persisting
  198. # on disk properly, otherwise chances are that no one will notice and some
  199. # disaster will happen.
  200. #
  201. # If the background saving process will start working again Redis will
  202. # automatically allow writes again.
  203. #
  204. # However if you have setup your proper monitoring of the Redis server
  205. # and persistence, you may want to disable this feature so that Redis will
  206. # continue to work as usual even if there are problems with disk,
  207. # permissions, and so forth.
  208. stop-writes-on-bgsave-error yes
  209. # Compress string objects using LZF when dump .rdb databases?
  210. # For default that's set to 'yes' as it's almost always a win.
  211. # If you want to save some CPU in the saving child set it to 'no' but
  212. # the dataset will likely be bigger if you have compressible values or keys.
  213. rdbcompression yes
  214. # Since version 5 of RDB a CRC64 checksum is placed at the end of the file.
  215. # This makes the format more resistant to corruption but there is a performance
  216. # hit to pay (around 10%) when saving and loading RDB files, so you can disable it
  217. # for maximum performances.
  218. #
  219. # RDB files created with checksum disabled have a checksum of zero that will
  220. # tell the loading code to skip the check.
  221. rdbchecksum yes
  222. # The filename where to dump the DB
  223. dbfilename dump.rdb
  224. # The working directory.
  225. #
  226. # The DB will be written inside this directory, with the filename specified
  227. # above using the 'dbfilename' configuration directive.
  228. #
  229. # The Append Only File will also be created inside this directory.
  230. #
  231. # Note that you must specify a directory here, not a file name.
  232. dir ./
  233. ################################# REPLICATION #################################
  234. # Master-Replica replication. Use replicaof to make a Redis instance a copy of
  235. # another Redis server. A few things to understand ASAP about Redis replication.
  236. #
  237. # +------------------+ +---------------+
  238. # | Master | ---> | Replica |
  239. # | (receive writes) | | (exact copy) |
  240. # +------------------+ +---------------+
  241. #
  242. # 1) Redis replication is asynchronous, but you can configure a master to
  243. # stop accepting writes if it appears to be not connected with at least
  244. # a given number of replicas.
  245. # 2) Redis replicas are able to perform a partial resynchronization with the
  246. # master if the replication link is lost for a relatively small amount of
  247. # time. You may want to configure the replication backlog size (see the next
  248. # sections of this file) with a sensible value depending on your needs.
  249. # 3) Replication is automatic and does not need user intervention. After a
  250. # network partition replicas automatically try to reconnect to masters
  251. # and resynchronize with them.
  252. #
  253. # replicaof <masterip> <masterport>
  254. # If the master is password protected (using the "requirepass" configuration
  255. # directive below) it is possible to tell the replica to authenticate before
  256. # starting the replication synchronization process, otherwise the master will
  257. # refuse the replica request.
  258. #
  259. # masterauth <master-password>
  260. #
  261. # However this is not enough if you are using Redis ACLs (for Redis version
  262. # 6 or greater), and the default user is not capable of running the PSYNC
  263. # command and/or other commands needed for replication. In this case it's
  264. # better to configure a special user to use with replication, and specify the
  265. # masteruser configuration as such:
  266. #
  267. # masteruser <username>
  268. #
  269. # When masteruser is specified, the replica will authenticate against its
  270. # master using the new AUTH form: AUTH <username> <password>.
  271. # When a replica loses its connection with the master, or when the replication
  272. # is still in progress, the replica can act in two different ways:
  273. #
  274. # 1) if replica-serve-stale-data is set to 'yes' (the default) the replica will
  275. # still reply to client requests, possibly with out of date data, or the
  276. # data set may just be empty if this is the first synchronization.
  277. #
  278. # 2) if replica-serve-stale-data is set to 'no' the replica will reply with
  279. # an error "SYNC with master in progress" to all the kind of commands
  280. # but to INFO, replicaOF, AUTH, PING, SHUTDOWN, REPLCONF, ROLE, CONFIG,
  281. # SUBSCRIBE, UNSUBSCRIBE, PSUBSCRIBE, PUNSUBSCRIBE, PUBLISH, PUBSUB,
  282. # COMMAND, POST, HOST: and LATENCY.
  283. #
  284. replica-serve-stale-data yes
  285. # You can configure a replica instance to accept writes or not. Writing against
  286. # a replica instance may be useful to store some ephemeral data (because data
  287. # written on a replica will be easily deleted after resync with the master) but
  288. # may also cause problems if clients are writing to it because of a
  289. # misconfiguration.
  290. #
  291. # Since Redis 2.6 by default replicas are read-only.
  292. #
  293. # Note: read only replicas are not designed to be exposed to untrusted clients
  294. # on the internet. It's just a protection layer against misuse of the instance.
  295. # Still a read only replica exports by default all the administrative commands
  296. # such as CONFIG, DEBUG, and so forth. To a limited extent you can improve
  297. # security of read only replicas using 'rename-command' to shadow all the
  298. # administrative / dangerous commands.
  299. replica-read-only yes
  300. # Replication SYNC strategy: disk or socket.
  301. #
  302. # New replicas and reconnecting replicas that are not able to continue the
  303. # replication process just receiving differences, need to do what is called a
  304. # "full synchronization". An RDB file is transmitted from the master to the
  305. # replicas.
  306. #
  307. # The transmission can happen in two different ways:
  308. #
  309. # 1) Disk-backed: The Redis master creates a new process that writes the RDB
  310. # file on disk. Later the file is transferred by the parent
  311. # process to the replicas incrementally.
  312. # 2) Diskless: The Redis master creates a new process that directly writes the
  313. # RDB file to replica sockets, without touching the disk at all.
  314. #
  315. # With disk-backed replication, while the RDB file is generated, more replicas
  316. # can be queued and served with the RDB file as soon as the current child
  317. # producing the RDB file finishes its work. With diskless replication instead
  318. # once the transfer starts, new replicas arriving will be queued and a new
  319. # transfer will start when the current one terminates.
  320. #
  321. # When diskless replication is used, the master waits a configurable amount of
  322. # time (in seconds) before starting the transfer in the hope that multiple
  323. # replicas will arrive and the transfer can be parallelized.
  324. #
  325. # With slow disks and fast (large bandwidth) networks, diskless replication
  326. # works better.
  327. repl-diskless-sync no
  328. # When diskless replication is enabled, it is possible to configure the delay
  329. # the server waits in order to spawn the child that transfers the RDB via socket
  330. # to the replicas.
  331. #
  332. # This is important since once the transfer starts, it is not possible to serve
  333. # new replicas arriving, that will be queued for the next RDB transfer, so the
  334. # server waits a delay in order to let more replicas arrive.
  335. #
  336. # The delay is specified in seconds, and by default is 5 seconds. To disable
  337. # it entirely just set it to 0 seconds and the transfer will start ASAP.
  338. repl-diskless-sync-delay 5
  339. # -----------------------------------------------------------------------------
  340. # WARNING: RDB diskless load is experimental. Since in this setup the replica
  341. # does not immediately store an RDB on disk, it may cause data loss during
  342. # failovers. RDB diskless load + Redis modules not handling I/O reads may also
  343. # cause Redis to abort in case of I/O errors during the initial synchronization
  344. # stage with the master. Use only if your do what you are doing.
  345. # -----------------------------------------------------------------------------
  346. #
  347. # Replica can load the RDB it reads from the replication link directly from the
  348. # socket, or store the RDB to a file and read that file after it was completely
  349. # recived from the master.
  350. #
  351. # In many cases the disk is slower than the network, and storing and loading
  352. # the RDB file may increase replication time (and even increase the master's
  353. # Copy on Write memory and salve buffers).
  354. # However, parsing the RDB file directly from the socket may mean that we have
  355. # to flush the contents of the current database before the full rdb was
  356. # received. For this reason we have the following options:
  357. #
  358. # "disabled" - Don't use diskless load (store the rdb file to the disk first)
  359. # "on-empty-db" - Use diskless load only when it is completely safe.
  360. # "swapdb" - Keep a copy of the current db contents in RAM while parsing
  361. # the data directly from the socket. note that this requires
  362. # sufficient memory, if you don't have it, you risk an OOM kill.
  363. repl-diskless-load disabled
  364. # Replicas send PINGs to server in a predefined interval. It's possible to
  365. # change this interval with the repl_ping_replica_period option. The default
  366. # value is 10 seconds.
  367. #
  368. # repl-ping-replica-period 10
  369. # The following option sets the replication timeout for:
  370. #
  371. # 1) Bulk transfer I/O during SYNC, from the point of view of replica.
  372. # 2) Master timeout from the point of view of replicas (data, pings).
  373. # 3) Replica timeout from the point of view of masters (REPLCONF ACK pings).
  374. #
  375. # It is important to make sure that this value is greater than the value
  376. # specified for repl-ping-replica-period otherwise a timeout will be detected
  377. # every time there is low traffic between the master and the replica.
  378. #
  379. # repl-timeout 60
  380. # Disable TCP_NODELAY on the replica socket after SYNC?
  381. #
  382. # If you select "yes" Redis will use a smaller number of TCP packets and
  383. # less bandwidth to send data to replicas. But this can add a delay for
  384. # the data to appear on the replica side, up to 40 milliseconds with
  385. # Linux kernels using a default configuration.
  386. #
  387. # If you select "no" the delay for data to appear on the replica side will
  388. # be reduced but more bandwidth will be used for replication.
  389. #
  390. # By default we optimize for low latency, but in very high traffic conditions
  391. # or when the master and replicas are many hops away, turning this to "yes" may
  392. # be a good idea.
  393. repl-disable-tcp-nodelay no
  394. # Set the replication backlog size. The backlog is a buffer that accumulates
  395. # replica data when replicas are disconnected for some time, so that when a
  396. # replica wants to reconnect again, often a full resync is not needed, but a
  397. # partial resync is enough, just passing the portion of data the replica
  398. # missed while disconnected.
  399. #
  400. # The bigger the replication backlog, the longer the time the replica can be
  401. # disconnected and later be able to perform a partial resynchronization.
  402. #
  403. # The backlog is only allocated once there is at least a replica connected.
  404. #
  405. # repl-backlog-size 1mb
  406. # After a master has no longer connected replicas for some time, the backlog
  407. # will be freed. The following option configures the amount of seconds that
  408. # need to elapse, starting from the time the last replica disconnected, for
  409. # the backlog buffer to be freed.
  410. #
  411. # Note that replicas never free the backlog for timeout, since they may be
  412. # promoted to masters later, and should be able to correctly "partially
  413. # resynchronize" with the replicas: hence they should always accumulate backlog.
  414. #
  415. # A value of 0 means to never release the backlog.
  416. #
  417. # repl-backlog-ttl 3600
  418. # The replica priority is an integer number published by Redis in the INFO
  419. # output. It is used by Redis Sentinel in order to select a replica to promote
  420. # into a master if the master is no longer working correctly.
  421. #
  422. # A replica with a low priority number is considered better for promotion, so
  423. # for instance if there are three replicas with priority 10, 100, 25 Sentinel
  424. # will pick the one with priority 10, that is the lowest.
  425. #
  426. # However a special priority of 0 marks the replica as not able to perform the
  427. # role of master, so a replica with priority of 0 will never be selected by
  428. # Redis Sentinel for promotion.
  429. #
  430. # By default the priority is 100.
  431. replica-priority 100
  432. # It is possible for a master to stop accepting writes if there are less than
  433. # N replicas connected, having a lag less or equal than M seconds.
  434. #
  435. # The N replicas need to be in "online" state.
  436. #
  437. # The lag in seconds, that must be <= the specified value, is calculated from
  438. # the last ping received from the replica, that is usually sent every second.
  439. #
  440. # This option does not GUARANTEE that N replicas will accept the write, but
  441. # will limit the window of exposure for lost writes in case not enough replicas
  442. # are available, to the specified number of seconds.
  443. #
  444. # For example to require at least 3 replicas with a lag <= 10 seconds use:
  445. #
  446. # min-replicas-to-write 3
  447. # min-replicas-max-lag 10
  448. #
  449. # Setting one or the other to 0 disables the feature.
  450. #
  451. # By default min-replicas-to-write is set to 0 (feature disabled) and
  452. # min-replicas-max-lag is set to 10.
  453. # A Redis master is able to list the address and port of the attached
  454. # replicas in different ways. For example the "INFO replication" section
  455. # offers this information, which is used, among other tools, by
  456. # Redis Sentinel in order to discover replica instances.
  457. # Another place where this info is available is in the output of the
  458. # "ROLE" command of a master.
  459. #
  460. # The listed IP and address normally reported by a replica is obtained
  461. # in the following way:
  462. #
  463. # IP: The address is auto detected by checking the peer address
  464. # of the socket used by the replica to connect with the master.
  465. #
  466. # Port: The port is communicated by the replica during the replication
  467. # handshake, and is normally the port that the replica is using to
  468. # listen for connections.
  469. #
  470. # However when port forwarding or Network Address Translation (NAT) is
  471. # used, the replica may be actually reachable via different IP and port
  472. # pairs. The following two options can be used by a replica in order to
  473. # report to its master a specific set of IP and port, so that both INFO
  474. # and ROLE will report those values.
  475. #
  476. # There is no need to use both the options if you need to override just
  477. # the port or the IP address.
  478. #
  479. # replica-announce-ip 5.5.5.5
  480. # replica-announce-port 1234
  481. ############################### KEYS TRACKING #################################
  482. # Redis implements server assisted support for client side caching of values.
  483. # This is implemented using an invalidation table that remembers, using
  484. # 16 millions of slots, what clients may have certain subsets of keys. In turn
  485. # this is used in order to send invalidation messages to clients. Please
  486. # to understand more about the feature check this page:
  487. #
  488. # https://redis.io/topics/client-side-caching
  489. #
  490. # When tracking is enabled for a client, all the read only queries are assumed
  491. # to be cached: this will force Redis to store information in the invalidation
  492. # table. When keys are modified, such information is flushed away, and
  493. # invalidation messages are sent to the clients. However if the workload is
  494. # heavily dominated by reads, Redis could use more and more memory in order
  495. # to track the keys fetched by many clients.
  496. #
  497. # For this reason it is possible to configure a maximum fill value for the
  498. # invalidation table. By default it is set to 10%, and once this limit is
  499. # reached, Redis will start to evict caching slots in the invalidation table
  500. # even if keys are not modified, just to reclaim memory: this will in turn
  501. # force the clients to invalidate the cached values. Basically the table
  502. # maximum fill rate is a trade off between the memory you want to spend server
  503. # side to track information about who cached what, and the ability of clients
  504. # to retain cached objects in memory.
  505. #
  506. # If you set the value to 0, it means there are no limits, and all the 16
  507. # millions of caching slots can be used at the same time. In the "stats"
  508. # INFO section, you can find information about the amount of caching slots
  509. # used at every given moment.
  510. #
  511. # tracking-table-max-fill 10
  512. ################################## SECURITY ###################################
  513. # Warning: since Redis is pretty fast an outside user can try up to
  514. # 1 million passwords per second against a modern box. This means that you
  515. # should use very strong passwords, otherwise they will be very easy to break.
  516. # Note that because the password is really a shared secret between the client
  517. # and the server, and should not be memorized by any human, the password
  518. # can be easily a long string from /dev/urandom or whatever, so by using a
  519. # long and unguessable password no brute force attack will be possible.
  520. # Redis ACL users are defined in the following format:
  521. #
  522. # user <username> ... acl rules ...
  523. #
  524. # For example:
  525. #
  526. # user worker +@list +@connection ~jobs:* on >ffa9203c493aa99
  527. #
  528. # The special username "default" is used for new connections. If this user
  529. # has the "nopass" rule, then new connections will be immediately authenticated
  530. # as the "default" user without the need of any password provided via the
  531. # AUTH command. Otherwise if the "default" user is not flagged with "nopass"
  532. # the connections will start in not authenticated state, and will require
  533. # AUTH (or the HELLO command AUTH option) in order to be authenticated and
  534. # start to work.
  535. #
  536. # The ACL rules that describe what an user can do are the following:
  537. #
  538. # on Enable the user: it is possible to authenticate as this user.
  539. # off Disable the user: it's no longer possible to authenticate
  540. # with this user, however the already authenticated connections
  541. # will still work.
  542. # +<command> Allow the execution of that command
  543. # -<command> Disallow the execution of that command
  544. # +@<category> Allow the execution of all the commands in such category
  545. # with valid categories are like @admin, @set, @sortedset, ...
  546. # and so forth, see the full list in the server.c file where
  547. # the Redis command table is described and defined.
  548. # The special category @all means all the commands, but currently
  549. # present in the server, and that will be loaded in the future
  550. # via modules.
  551. # +<command>|subcommand Allow a specific subcommand of an otherwise
  552. # disabled command. Note that this form is not
  553. # allowed as negative like -DEBUG|SEGFAULT, but
  554. # only additive starting with "+".
  555. # allcommands Alias for +@all. Note that it implies the ability to execute
  556. # all the future commands loaded via the modules system.
  557. # nocommands Alias for -@all.
  558. # ~<pattern> Add a pattern of keys that can be mentioned as part of
  559. # commands. For instance ~* allows all the keys. The pattern
  560. # is a glob-style pattern like the one of KEYS.
  561. # It is possible to specify multiple patterns.
  562. # allkeys Alias for ~*
  563. # resetkeys Flush the list of allowed keys patterns.
  564. # ><password> Add this passowrd to the list of valid password for the user.
  565. # For example >mypass will add "mypass" to the list.
  566. # This directive clears the "nopass" flag (see later).
  567. # <<password> Remove this password from the list of valid passwords.
  568. # nopass All the set passwords of the user are removed, and the user
  569. # is flagged as requiring no password: it means that every
  570. # password will work against this user. If this directive is
  571. # used for the default user, every new connection will be
  572. # immediately authenticated with the default user without
  573. # any explicit AUTH command required. Note that the "resetpass"
  574. # directive will clear this condition.
  575. # resetpass Flush the list of allowed passwords. Moreover removes the
  576. # "nopass" status. After "resetpass" the user has no associated
  577. # passwords and there is no way to authenticate without adding
  578. # some password (or setting it as "nopass" later).
  579. # reset Performs the following actions: resetpass, resetkeys, off,
  580. # -@all. The user returns to the same state it has immediately
  581. # after its creation.
  582. #
  583. # ACL rules can be specified in any order: for instance you can start with
  584. # passwords, then flags, or key patterns. However note that the additive
  585. # and subtractive rules will CHANGE MEANING depending on the ordering.
  586. # For instance see the following example:
  587. #
  588. # user alice on +@all -DEBUG ~* >somepassword
  589. #
  590. # This will allow "alice" to use all the commands with the exception of the
  591. # DEBUG command, since +@all added all the commands to the set of the commands
  592. # alice can use, and later DEBUG was removed. However if we invert the order
  593. # of two ACL rules the result will be different:
  594. #
  595. # user alice on -DEBUG +@all ~* >somepassword
  596. #
  597. # Now DEBUG was removed when alice had yet no commands in the set of allowed
  598. # commands, later all the commands are added, so the user will be able to
  599. # execute everything.
  600. #
  601. # Basically ACL rules are processed left-to-right.
  602. #
  603. # For more information about ACL configuration please refer to
  604. # the Redis web site at https://redis.io/topics/acl
  605. # Using an external ACL file
  606. #
  607. # Instead of configuring users here in this file, it is possible to use
  608. # a stand-alone file just listing users. The two methods cannot be mixed:
  609. # if you configure users here and at the same time you activate the exteranl
  610. # ACL file, the server will refuse to start.
  611. #
  612. # The format of the external ACL user file is exactly the same as the
  613. # format that is used inside redis.conf to describe users.
  614. #
  615. # aclfile /etc/redis/users.acl
  616. # IMPORTANT NOTE: starting with Redis 6 "requirepass" is just a compatiblity
  617. # layer on top of the new ACL system. The option effect will be just setting
  618. # the password for the default user. Clients will still authenticate using
  619. # AUTH <password> as usually, or more explicitly with AUTH default <password>
  620. # if they follow the new protocol: both will work.
  621. #
  622. # requirepass foobared
  623. # Command renaming (DEPRECATED).
  624. #
  625. # ------------------------------------------------------------------------
  626. # WARNING: avoid using this option if possible. Instead use ACLs to remove
  627. # commands from the default user, and put them only in some admin user you
  628. # create for administrative purposes.
  629. # ------------------------------------------------------------------------
  630. #
  631. # It is possible to change the name of dangerous commands in a shared
  632. # environment. For instance the CONFIG command may be renamed into something
  633. # hard to guess so that it will still be available for internal-use tools
  634. # but not available for general clients.
  635. #
  636. # Example:
  637. #
  638. # rename-command CONFIG b840fc02d524045429941cc15f59e41cb7be6c52
  639. #
  640. # It is also possible to completely kill a command by renaming it into
  641. # an empty string:
  642. #
  643. # rename-command CONFIG ""
  644. #
  645. # Please note that changing the name of commands that are logged into the
  646. # AOF file or transmitted to replicas may cause problems.
  647. ################################### CLIENTS ####################################
  648. # Set the max number of connected clients at the same time. By default
  649. # this limit is set to 10000 clients, however if the Redis server is not
  650. # able to configure the process file limit to allow for the specified limit
  651. # the max number of allowed clients is set to the current file limit
  652. # minus 32 (as Redis reserves a few file descriptors for internal uses).
  653. #
  654. # Once the limit is reached Redis will close all the new connections sending
  655. # an error 'max number of clients reached'.
  656. #
  657. # maxclients 10000
  658. ############################## MEMORY MANAGEMENT ################################
  659. # Set a memory usage limit to the specified amount of bytes.
  660. # When the memory limit is reached Redis will try to remove keys
  661. # according to the eviction policy selected (see maxmemory-policy).
  662. #
  663. # If Redis can't remove keys according to the policy, or if the policy is
  664. # set to 'noeviction', Redis will start to reply with errors to commands
  665. # that would use more memory, like SET, LPUSH, and so on, and will continue
  666. # to reply to read-only commands like GET.
  667. #
  668. # This option is usually useful when using Redis as an LRU or LFU cache, or to
  669. # set a hard memory limit for an instance (using the 'noeviction' policy).
  670. #
  671. # WARNING: If you have replicas attached to an instance with maxmemory on,
  672. # the size of the output buffers needed to feed the replicas are subtracted
  673. # from the used memory count, so that network problems / resyncs will
  674. # not trigger a loop where keys are evicted, and in turn the output
  675. # buffer of replicas is full with DELs of keys evicted triggering the deletion
  676. # of more keys, and so forth until the database is completely emptied.
  677. #
  678. # In short... if you have replicas attached it is suggested that you set a lower
  679. # limit for maxmemory so that there is some free RAM on the system for replica
  680. # output buffers (but this is not needed if the policy is 'noeviction').
  681. #
  682. # maxmemory <bytes>
  683. # MAXMEMORY POLICY: how Redis will select what to remove when maxmemory
  684. # is reached. You can select among five behaviors:
  685. #
  686. # volatile-lru -> Evict using approximated LRU among the keys with an expire set.
  687. # allkeys-lru -> Evict any key using approximated LRU.
  688. # volatile-lfu -> Evict using approximated LFU among the keys with an expire set.
  689. # allkeys-lfu -> Evict any key using approximated LFU.
  690. # volatile-random -> Remove a random key among the ones with an expire set.
  691. # allkeys-random -> Remove a random key, any key.
  692. # volatile-ttl -> Remove the key with the nearest expire time (minor TTL)
  693. # noeviction -> Don't evict anything, just return an error on write operations.
  694. #
  695. # LRU means Least Recently Used
  696. # LFU means Least Frequently Used
  697. #
  698. # Both LRU, LFU and volatile-ttl are implemented using approximated
  699. # randomized algorithms.
  700. #
  701. # Note: with any of the above policies, Redis will return an error on write
  702. # operations, when there are no suitable keys for eviction.
  703. #
  704. # At the date of writing these commands are: set setnx setex append
  705. # incr decr rpush lpush rpushx lpushx linsert lset rpoplpush sadd
  706. # sinter sinterstore sunion sunionstore sdiff sdiffstore zadd zincrby
  707. # zunionstore zinterstore hset hsetnx hmset hincrby incrby decrby
  708. # getset mset msetnx exec sort
  709. #
  710. # The default is:
  711. #
  712. # maxmemory-policy noeviction
  713. # LRU, LFU and minimal TTL algorithms are not precise algorithms but approximated
  714. # algorithms (in order to save memory), so you can tune it for speed or
  715. # accuracy. For default Redis will check five keys and pick the one that was
  716. # used less recently, you can change the sample size using the following
  717. # configuration directive.
  718. #
  719. # The default of 5 produces good enough results. 10 Approximates very closely
  720. # true LRU but costs more CPU. 3 is faster but not very accurate.
  721. #
  722. # maxmemory-samples 5
  723. # Starting from Redis 5, by default a replica will ignore its maxmemory setting
  724. # (unless it is promoted to master after a failover or manually). It means
  725. # that the eviction of keys will be just handled by the master, sending the
  726. # DEL commands to the replica as keys evict in the master side.
  727. #
  728. # This behavior ensures that masters and replicas stay consistent, and is usually
  729. # what you want, however if your replica is writable, or you want the replica
  730. # to have a different memory setting, and you are sure all the writes performed
  731. # to the replica are idempotent, then you may change this default (but be sure
  732. # to understand what you are doing).
  733. #
  734. # Note that since the replica by default does not evict, it may end using more
  735. # memory than the one set via maxmemory (there are certain buffers that may
  736. # be larger on the replica, or data structures may sometimes take more memory
  737. # and so forth). So make sure you monitor your replicas and make sure they
  738. # have enough memory to never hit a real out-of-memory condition before the
  739. # master hits the configured maxmemory setting.
  740. #
  741. # replica-ignore-maxmemory yes
  742. ############################# LAZY FREEING ####################################
  743. # Redis has two primitives to delete keys. One is called DEL and is a blocking
  744. # deletion of the object. It means that the server stops processing new commands
  745. # in order to reclaim all the memory associated with an object in a synchronous
  746. # way. If the key deleted is associated with a small object, the time needed
  747. # in order to execute the DEL command is very small and comparable to most other
  748. # O(1) or O(log_N) commands in Redis. However if the key is associated with an
  749. # aggregated value containing millions of elements, the server can block for
  750. # a long time (even seconds) in order to complete the operation.
  751. #
  752. # For the above reasons Redis also offers non blocking deletion primitives
  753. # such as UNLINK (non blocking DEL) and the ASYNC option of FLUSHALL and
  754. # FLUSHDB commands, in order to reclaim memory in background. Those commands
  755. # are executed in constant time. Another thread will incrementally free the
  756. # object in the background as fast as possible.
  757. #
  758. # DEL, UNLINK and ASYNC option of FLUSHALL and FLUSHDB are user-controlled.
  759. # It's up to the design of the application to understand when it is a good
  760. # idea to use one or the other. However the Redis server sometimes has to
  761. # delete keys or flush the whole database as a side effect of other operations.
  762. # Specifically Redis deletes objects independently of a user call in the
  763. # following scenarios:
  764. #
  765. # 1) On eviction, because of the maxmemory and maxmemory policy configurations,
  766. # in order to make room for new data, without going over the specified
  767. # memory limit.
  768. # 2) Because of expire: when a key with an associated time to live (see the
  769. # EXPIRE command) must be deleted from memory.
  770. # 3) Because of a side effect of a command that stores data on a key that may
  771. # already exist. For example the RENAME command may delete the old key
  772. # content when it is replaced with another one. Similarly SUNIONSTORE
  773. # or SORT with STORE option may delete existing keys. The SET command
  774. # itself removes any old content of the specified key in order to replace
  775. # it with the specified string.
  776. # 4) During replication, when a replica performs a full resynchronization with
  777. # its master, the content of the whole database is removed in order to
  778. # load the RDB file just transferred.
  779. #
  780. # In all the above cases the default is to delete objects in a blocking way,
  781. # like if DEL was called. However you can configure each case specifically
  782. # in order to instead release memory in a non-blocking way like if UNLINK
  783. # was called, using the following configuration directives:
  784. lazyfree-lazy-eviction no
  785. lazyfree-lazy-expire no
  786. lazyfree-lazy-server-del no
  787. replica-lazy-flush no
  788. ############################## APPEND ONLY MODE ###############################
  789. # By default Redis asynchronously dumps the dataset on disk. This mode is
  790. # good enough in many applications, but an issue with the Redis process or
  791. # a power outage may result into a few minutes of writes lost (depending on
  792. # the configured save points).
  793. #
  794. # The Append Only File is an alternative persistence mode that provides
  795. # much better durability. For instance using the default data fsync policy
  796. # (see later in the config file) Redis can lose just one second of writes in a
  797. # dramatic event like a server power outage, or a single write if something
  798. # wrong with the Redis process itself happens, but the operating system is
  799. # still running correctly.
  800. #
  801. # AOF and RDB persistence can be enabled at the same time without problems.
  802. # If the AOF is enabled on startup Redis will load the AOF, that is the file
  803. # with the better durability guarantees.
  804. #
  805. # Please check http://redis.io/topics/persistence for more information.
  806. appendonly no
  807. # The name of the append only file (default: "appendonly.aof")
  808. appendfilename "appendonly.aof"
  809. # The fsync() call tells the Operating System to actually write data on disk
  810. # instead of waiting for more data in the output buffer. Some OS will really flush
  811. # data on disk, some other OS will just try to do it ASAP.
  812. #
  813. # Redis supports three different modes:
  814. #
  815. # no: don't fsync, just let the OS flush the data when it wants. Faster.
  816. # always: fsync after every write to the append only log. Slow, Safest.
  817. # everysec: fsync only one time every second. Compromise.
  818. #
  819. # The default is "everysec", as that's usually the right compromise between
  820. # speed and data safety. It's up to you to understand if you can relax this to
  821. # "no" that will let the operating system flush the output buffer when
  822. # it wants, for better performances (but if you can live with the idea of
  823. # some data loss consider the default persistence mode that's snapshotting),
  824. # or on the contrary, use "always" that's very slow but a bit safer than
  825. # everysec.
  826. #
  827. # More details please check the following article:
  828. # http://antirez.com/post/redis-persistence-demystified.html
  829. #
  830. # If unsure, use "everysec".
  831. # appendfsync always
  832. appendfsync everysec
  833. # appendfsync no
  834. # When the AOF fsync policy is set to always or everysec, and a background
  835. # saving process (a background save or AOF log background rewriting) is
  836. # performing a lot of I/O against the disk, in some Linux configurations
  837. # Redis may block too long on the fsync() call. Note that there is no fix for
  838. # this currently, as even performing fsync in a different thread will block
  839. # our synchronous write(2) call.
  840. #
  841. # In order to mitigate this problem it's possible to use the following option
  842. # that will prevent fsync() from being called in the main process while a
  843. # BGSAVE or BGREWRITEAOF is in progress.
  844. #
  845. # This means that while another child is saving, the durability of Redis is
  846. # the same as "appendfsync none". In practical terms, this means that it is
  847. # possible to lose up to 30 seconds of log in the worst scenario (with the
  848. # default Linux settings).
  849. #
  850. # If you have latency problems turn this to "yes". Otherwise leave it as
  851. # "no" that is the safest pick from the point of view of durability.
  852. no-appendfsync-on-rewrite no
  853. # Automatic rewrite of the append only file.
  854. # Redis is able to automatically rewrite the log file implicitly calling
  855. # BGREWRITEAOF when the AOF log size grows by the specified percentage.
  856. #
  857. # This is how it works: Redis remembers the size of the AOF file after the
  858. # latest rewrite (if no rewrite has happened since the restart, the size of
  859. # the AOF at startup is used).
  860. #
  861. # This base size is compared to the current size. If the current size is
  862. # bigger than the specified percentage, the rewrite is triggered. Also
  863. # you need to specify a minimal size for the AOF file to be rewritten, this
  864. # is useful to avoid rewriting the AOF file even if the percentage increase
  865. # is reached but it is still pretty small.
  866. #
  867. # Specify a percentage of zero in order to disable the automatic AOF
  868. # rewrite feature.
  869. auto-aof-rewrite-percentage 100
  870. auto-aof-rewrite-min-size 64mb
  871. # An AOF file may be found to be truncated at the end during the Redis
  872. # startup process, when the AOF data gets loaded back into memory.
  873. # This may happen when the system where Redis is running
  874. # crashes, especially when an ext4 filesystem is mounted without the
  875. # data=ordered option (however this can't happen when Redis itself
  876. # crashes or aborts but the operating system still works correctly).
  877. #
  878. # Redis can either exit with an error when this happens, or load as much
  879. # data as possible (the default now) and start if the AOF file is found
  880. # to be truncated at the end. The following option controls this behavior.
  881. #
  882. # If aof-load-truncated is set to yes, a truncated AOF file is loaded and
  883. # the Redis server starts emitting a log to inform the user of the event.
  884. # Otherwise if the option is set to no, the server aborts with an error
  885. # and refuses to start. When the option is set to no, the user requires
  886. # to fix the AOF file using the "redis-check-aof" utility before to restart
  887. # the server.
  888. #
  889. # Note that if the AOF file will be found to be corrupted in the middle
  890. # the server will still exit with an error. This option only applies when
  891. # Redis will try to read more data from the AOF file but not enough bytes
  892. # will be found.
  893. aof-load-truncated yes
  894. # When rewriting the AOF file, Redis is able to use an RDB preamble in the
  895. # AOF file for faster rewrites and recoveries. When this option is turned
  896. # on the rewritten AOF file is composed of two different stanzas:
  897. #
  898. # [RDB file][AOF tail]
  899. #
  900. # When loading Redis recognizes that the AOF file starts with the "REDIS"
  901. # string and loads the prefixed RDB file, and continues loading the AOF
  902. # tail.
  903. aof-use-rdb-preamble yes
  904. ################################ LUA SCRIPTING ###############################
  905. # Max execution time of a Lua script in milliseconds.
  906. #
  907. # If the maximum execution time is reached Redis will log that a script is
  908. # still in execution after the maximum allowed time and will start to
  909. # reply to queries with an error.
  910. #
  911. # When a long running script exceeds the maximum execution time only the
  912. # SCRIPT KILL and SHUTDOWN NOSAVE commands are available. The first can be
  913. # used to stop a script that did not yet called write commands. The second
  914. # is the only way to shut down the server in the case a write command was
  915. # already issued by the script but the user doesn't want to wait for the natural
  916. # termination of the script.
  917. #
  918. # Set it to 0 or a negative value for unlimited execution without warnings.
  919. lua-time-limit 5000
  920. ################################ REDIS CLUSTER ###############################
  921. # Normal Redis instances can't be part of a Redis Cluster; only nodes that are
  922. # started as cluster nodes can. In order to start a Redis instance as a
  923. # cluster node enable the cluster support uncommenting the following:
  924. #
  925. # cluster-enabled yes
  926. # Every cluster node has a cluster configuration file. This file is not
  927. # intended to be edited by hand. It is created and updated by Redis nodes.
  928. # Every Redis Cluster node requires a different cluster configuration file.
  929. # Make sure that instances running in the same system do not have
  930. # overlapping cluster configuration file names.
  931. #
  932. # cluster-config-file nodes-6379.conf
  933. # Cluster node timeout is the amount of milliseconds a node must be unreachable
  934. # for it to be considered in failure state.
  935. # Most other internal time limits are multiple of the node timeout.
  936. #
  937. # cluster-node-timeout 15000
  938. # A replica of a failing master will avoid to start a failover if its data
  939. # looks too old.
  940. #
  941. # There is no simple way for a replica to actually have an exact measure of
  942. # its "data age", so the following two checks are performed:
  943. #
  944. # 1) If there are multiple replicas able to failover, they exchange messages
  945. # in order to try to give an advantage to the replica with the best
  946. # replication offset (more data from the master processed).
  947. # Replicas will try to get their rank by offset, and apply to the start
  948. # of the failover a delay proportional to their rank.
  949. #
  950. # 2) Every single replica computes the time of the last interaction with
  951. # its master. This can be the last ping or command received (if the master
  952. # is still in the "connected" state), or the time that elapsed since the
  953. # disconnection with the master (if the replication link is currently down).
  954. # If the last interaction is too old, the replica will not try to failover
  955. # at all.
  956. #
  957. # The point "2" can be tuned by user. Specifically a replica will not perform
  958. # the failover if, since the last interaction with the master, the time
  959. # elapsed is greater than:
  960. #
  961. # (node-timeout * replica-validity-factor) + repl-ping-replica-period
  962. #
  963. # So for example if node-timeout is 30 seconds, and the replica-validity-factor
  964. # is 10, and assuming a default repl-ping-replica-period of 10 seconds, the
  965. # replica will not try to failover if it was not able to talk with the master
  966. # for longer than 310 seconds.
  967. #
  968. # A large replica-validity-factor may allow replicas with too old data to failover
  969. # a master, while a too small value may prevent the cluster from being able to
  970. # elect a replica at all.
  971. #
  972. # For maximum availability, it is possible to set the replica-validity-factor
  973. # to a value of 0, which means, that replicas will always try to failover the
  974. # master regardless of the last time they interacted with the master.
  975. # (However they'll always try to apply a delay proportional to their
  976. # offset rank).
  977. #
  978. # Zero is the only value able to guarantee that when all the partitions heal
  979. # the cluster will always be able to continue.
  980. #
  981. # cluster-replica-validity-factor 10
  982. # Cluster replicas are able to migrate to orphaned masters, that are masters
  983. # that are left without working replicas. This improves the cluster ability
  984. # to resist to failures as otherwise an orphaned master can't be failed over
  985. # in case of failure if it has no working replicas.
  986. #
  987. # Replicas migrate to orphaned masters only if there are still at least a
  988. # given number of other working replicas for their old master. This number
  989. # is the "migration barrier". A migration barrier of 1 means that a replica
  990. # will migrate only if there is at least 1 other working replica for its master
  991. # and so forth. It usually reflects the number of replicas you want for every
  992. # master in your cluster.
  993. #
  994. # Default is 1 (replicas migrate only if their masters remain with at least
  995. # one replica). To disable migration just set it to a very large value.
  996. # A value of 0 can be set but is useful only for debugging and dangerous
  997. # in production.
  998. #
  999. # cluster-migration-barrier 1
  1000. # By default Redis Cluster nodes stop accepting queries if they detect there
  1001. # is at least an hash slot uncovered (no available node is serving it).
  1002. # This way if the cluster is partially down (for example a range of hash slots
  1003. # are no longer covered) all the cluster becomes, eventually, unavailable.
  1004. # It automatically returns available as soon as all the slots are covered again.
  1005. #
  1006. # However sometimes you want the subset of the cluster which is working,
  1007. # to continue to accept queries for the part of the key space that is still
  1008. # covered. In order to do so, just set the cluster-require-full-coverage
  1009. # option to no.
  1010. #
  1011. # cluster-require-full-coverage yes
  1012. # This option, when set to yes, prevents replicas from trying to failover its
  1013. # master during master failures. However the master can still perform a
  1014. # manual failover, if forced to do so.
  1015. #
  1016. # This is useful in different scenarios, especially in the case of multiple
  1017. # data center operations, where we want one side to never be promoted if not
  1018. # in the case of a total DC failure.
  1019. #
  1020. # cluster-replica-no-failover no
  1021. # In order to setup your cluster make sure to read the documentation
  1022. # available at http://redis.io web site.
  1023. ########################## CLUSTER DOCKER/NAT support ########################
  1024. # In certain deployments, Redis Cluster nodes address discovery fails, because
  1025. # addresses are NAT-ted or because ports are forwarded (the typical case is
  1026. # Docker and other containers).
  1027. #
  1028. # In order to make Redis Cluster working in such environments, a static
  1029. # configuration where each node knows its public address is needed. The
  1030. # following two options are used for this scope, and are:
  1031. #
  1032. # * cluster-announce-ip
  1033. # * cluster-announce-port
  1034. # * cluster-announce-bus-port
  1035. #
  1036. # Each instruct the node about its address, client port, and cluster message
  1037. # bus port. The information is then published in the header of the bus packets
  1038. # so that other nodes will be able to correctly map the address of the node
  1039. # publishing the information.
  1040. #
  1041. # If the above options are not used, the normal Redis Cluster auto-detection
  1042. # will be used instead.
  1043. #
  1044. # Note that when remapped, the bus port may not be at the fixed offset of
  1045. # clients port + 10000, so you can specify any port and bus-port depending
  1046. # on how they get remapped. If the bus-port is not set, a fixed offset of
  1047. # 10000 will be used as usually.
  1048. #
  1049. # Example:
  1050. #
  1051. # cluster-announce-ip 10.1.1.5
  1052. # cluster-announce-port 6379
  1053. # cluster-announce-bus-port 6380
  1054. ################################## SLOW LOG ###################################
  1055. # The Redis Slow Log is a system to log queries that exceeded a specified
  1056. # execution time. The execution time does not include the I/O operations
  1057. # like talking with the client, sending the reply and so forth,
  1058. # but just the time needed to actually execute the command (this is the only
  1059. # stage of command execution where the thread is blocked and can not serve
  1060. # other requests in the meantime).
  1061. #
  1062. # You can configure the slow log with two parameters: one tells Redis
  1063. # what is the execution time, in microseconds, to exceed in order for the
  1064. # command to get logged, and the other parameter is the length of the
  1065. # slow log. When a new command is logged the oldest one is removed from the
  1066. # queue of logged commands.
  1067. # The following time is expressed in microseconds, so 1000000 is equivalent
  1068. # to one second. Note that a negative number disables the slow log, while
  1069. # a value of zero forces the logging of every command.
  1070. slowlog-log-slower-than 10000
  1071. # There is no limit to this length. Just be aware that it will consume memory.
  1072. # You can reclaim memory used by the slow log with SLOWLOG RESET.
  1073. slowlog-max-len 128
  1074. ################################ LATENCY MONITOR ##############################
  1075. # The Redis latency monitoring subsystem samples different operations
  1076. # at runtime in order to collect data related to possible sources of
  1077. # latency of a Redis instance.
  1078. #
  1079. # Via the LATENCY command this information is available to the user that can
  1080. # print graphs and obtain reports.
  1081. #
  1082. # The system only logs operations that were performed in a time equal or
  1083. # greater than the amount of milliseconds specified via the
  1084. # latency-monitor-threshold configuration directive. When its value is set
  1085. # to zero, the latency monitor is turned off.
  1086. #
  1087. # By default latency monitoring is disabled since it is mostly not needed
  1088. # if you don't have latency issues, and collecting data has a performance
  1089. # impact, that while very small, can be measured under big load. Latency
  1090. # monitoring can easily be enabled at runtime using the command
  1091. # "CONFIG SET latency-monitor-threshold <milliseconds>" if needed.
  1092. latency-monitor-threshold 0
  1093. ############################# EVENT NOTIFICATION ##############################
  1094. # Redis can notify Pub/Sub clients about events happening in the key space.
  1095. # This feature is documented at http://redis.io/topics/notifications
  1096. #
  1097. # For instance if keyspace events notification is enabled, and a client
  1098. # performs a DEL operation on key "foo" stored in the Database 0, two
  1099. # messages will be published via Pub/Sub:
  1100. #
  1101. # PUBLISH __keyspace@0__:foo del
  1102. # PUBLISH __keyevent@0__:del foo
  1103. #
  1104. # It is possible to select the events that Redis will notify among a set
  1105. # of classes. Every class is identified by a single character:
  1106. #
  1107. # K Keyspace events, published with __keyspace@<db>__ prefix.
  1108. # E Keyevent events, published with __keyevent@<db>__ prefix.
  1109. # g Generic commands (non-type specific) like DEL, EXPIRE, RENAME, ...
  1110. # $ String commands
  1111. # l List commands
  1112. # s Set commands
  1113. # h Hash commands
  1114. # z Sorted set commands
  1115. # x Expired events (events generated every time a key expires)
  1116. # e Evicted events (events generated when a key is evicted for maxmemory)
  1117. # A Alias for g$lshzxe, so that the "AKE" string means all the events.
  1118. #
  1119. # The "notify-keyspace-events" takes as argument a string that is composed
  1120. # of zero or multiple characters. The empty string means that notifications
  1121. # are disabled.
  1122. #
  1123. # Example: to enable list and generic events, from the point of view of the
  1124. # event name, use:
  1125. #
  1126. # notify-keyspace-events Elg
  1127. #
  1128. # Example 2: to get the stream of the expired keys subscribing to channel
  1129. # name __keyevent@0__:expired use:
  1130. #
  1131. # notify-keyspace-events Ex
  1132. #
  1133. # By default all notifications are disabled because most users don't need
  1134. # this feature and the feature has some overhead. Note that if you don't
  1135. # specify at least one of K or E, no events will be delivered.
  1136. notify-keyspace-events ""
  1137. ############################### GOPHER SERVER #################################
  1138. # Redis contains an implementation of the Gopher protocol, as specified in
  1139. # the RFC 1436 (https://www.ietf.org/rfc/rfc1436.txt).
  1140. #
  1141. # The Gopher protocol was very popular in the late '90s. It is an alternative
  1142. # to the web, and the implementation both server and client side is so simple
  1143. # that the Redis server has just 100 lines of code in order to implement this
  1144. # support.
  1145. #
  1146. # What do you do with Gopher nowadays? Well Gopher never *really* died, and
  1147. # lately there is a movement in order for the Gopher more hierarchical content
  1148. # composed of just plain text documents to be resurrected. Some want a simpler
  1149. # internet, others believe that the mainstream internet became too much
  1150. # controlled, and it's cool to create an alternative space for people that
  1151. # want a bit of fresh air.
  1152. #
  1153. # Anyway for the 10nth birthday of the Redis, we gave it the Gopher protocol
  1154. # as a gift.
  1155. #
  1156. # --- HOW IT WORKS? ---
  1157. #
  1158. # The Redis Gopher support uses the inline protocol of Redis, and specifically
  1159. # two kind of inline requests that were anyway illegal: an empty request
  1160. # or any request that starts with "/" (there are no Redis commands starting
  1161. # with such a slash). Normal RESP2/RESP3 requests are completely out of the
  1162. # path of the Gopher protocol implementation and are served as usually as well.
  1163. #
  1164. # If you open a connection to Redis when Gopher is enabled and send it
  1165. # a string like "/foo", if there is a key named "/foo" it is served via the
  1166. # Gopher protocol.
  1167. #
  1168. # In order to create a real Gopher "hole" (the name of a Gopher site in Gopher
  1169. # talking), you likely need a script like the following:
  1170. #
  1171. # https://github.com/antirez/gopher2redis
  1172. #
  1173. # --- SECURITY WARNING ---
  1174. #
  1175. # If you plan to put Redis on the internet in a publicly accessible address
  1176. # to server Gopher pages MAKE SURE TO SET A PASSWORD to the instance.
  1177. # Once a password is set:
  1178. #
  1179. # 1. The Gopher server (when enabled, not by default) will kill serve
  1180. # content via Gopher.
  1181. # 2. However other commands cannot be called before the client will
  1182. # authenticate.
  1183. #
  1184. # So use the 'requirepass' option to protect your instance.
  1185. #
  1186. # To enable Gopher support uncomment the following line and set
  1187. # the option from no (the default) to yes.
  1188. #
  1189. # gopher-enabled no
  1190. ############################### ADVANCED CONFIG ###############################
  1191. # Hashes are encoded using a memory efficient data structure when they have a
  1192. # small number of entries, and the biggest entry does not exceed a given
  1193. # threshold. These thresholds can be configured using the following directives.
  1194. hash-max-ziplist-entries 512
  1195. hash-max-ziplist-value 64
  1196. # Lists are also encoded in a special way to save a lot of space.
  1197. # The number of entries allowed per internal list node can be specified
  1198. # as a fixed maximum size or a maximum number of elements.
  1199. # For a fixed maximum size, use -5 through -1, meaning:
  1200. # -5: max size: 64 Kb <-- not recommended for normal workloads
  1201. # -4: max size: 32 Kb <-- not recommended
  1202. # -3: max size: 16 Kb <-- probably not recommended
  1203. # -2: max size: 8 Kb <-- good
  1204. # -1: max size: 4 Kb <-- good
  1205. # Positive numbers mean store up to _exactly_ that number of elements
  1206. # per list node.
  1207. # The highest performing option is usually -2 (8 Kb size) or -1 (4 Kb size),
  1208. # but if your use case is unique, adjust the settings as necessary.
  1209. list-max-ziplist-size -2
  1210. # Lists may also be compressed.
  1211. # Compress depth is the number of quicklist ziplist nodes from *each* side of
  1212. # the list to *exclude* from compression. The head and tail of the list
  1213. # are always uncompressed for fast push/pop operations. Settings are:
  1214. # 0: disable all list compression
  1215. # 1: depth 1 means "don't start compressing until after 1 node into the list,
  1216. # going from either the head or tail"
  1217. # So: [head]->node->node->...->node->[tail]
  1218. # [head], [tail] will always be uncompressed; inner nodes will compress.
  1219. # 2: [head]->[next]->node->node->...->node->[prev]->[tail]
  1220. # 2 here means: don't compress head or head->next or tail->prev or tail,
  1221. # but compress all nodes between them.
  1222. # 3: [head]->[next]->[next]->node->node->...->node->[prev]->[prev]->[tail]
  1223. # etc.
  1224. list-compress-depth 0
  1225. # Sets have a special encoding in just one case: when a set is composed
  1226. # of just strings that happen to be integers in radix 10 in the range
  1227. # of 64 bit signed integers.
  1228. # The following configuration setting sets the limit in the size of the
  1229. # set in order to use this special memory saving encoding.
  1230. set-max-intset-entries 512
  1231. # Similarly to hashes and lists, sorted sets are also specially encoded in
  1232. # order to save a lot of space. This encoding is only used when the length and
  1233. # elements of a sorted set are below the following limits:
  1234. zset-max-ziplist-entries 128
  1235. zset-max-ziplist-value 64
  1236. # HyperLogLog sparse representation bytes limit. The limit includes the
  1237. # 16 bytes header. When an HyperLogLog using the sparse representation crosses
  1238. # this limit, it is converted into the dense representation.
  1239. #
  1240. # A value greater than 16000 is totally useless, since at that point the
  1241. # dense representation is more memory efficient.
  1242. #
  1243. # The suggested value is ~ 3000 in order to have the benefits of
  1244. # the space efficient encoding without slowing down too much PFADD,
  1245. # which is O(N) with the sparse encoding. The value can be raised to
  1246. # ~ 10000 when CPU is not a concern, but space is, and the data set is
  1247. # composed of many HyperLogLogs with cardinality in the 0 - 15000 range.
  1248. hll-sparse-max-bytes 3000
  1249. # Streams macro node max size / items. The stream data structure is a radix
  1250. # tree of big nodes that encode multiple items inside. Using this configuration
  1251. # it is possible to configure how big a single node can be in bytes, and the
  1252. # maximum number of items it may contain before switching to a new node when
  1253. # appending new stream entries. If any of the following settings are set to
  1254. # zero, the limit is ignored, so for instance it is possible to set just a
  1255. # max entires limit by setting max-bytes to 0 and max-entries to the desired
  1256. # value.
  1257. stream-node-max-bytes 4096
  1258. stream-node-max-entries 100
  1259. # Active rehashing uses 1 millisecond every 100 milliseconds of CPU time in
  1260. # order to help rehashing the main Redis hash table (the one mapping top-level
  1261. # keys to values). The hash table implementation Redis uses (see dict.c)
  1262. # performs a lazy rehashing: the more operation you run into a hash table
  1263. # that is rehashing, the more rehashing "steps" are performed, so if the
  1264. # server is idle the rehashing is never complete and some more memory is used
  1265. # by the hash table.
  1266. #
  1267. # The default is to use this millisecond 10 times every second in order to
  1268. # actively rehash the main dictionaries, freeing memory when possible.
  1269. #
  1270. # If unsure:
  1271. # use "activerehashing no" if you have hard latency requirements and it is
  1272. # not a good thing in your environment that Redis can reply from time to time
  1273. # to queries with 2 milliseconds delay.
  1274. #
  1275. # use "activerehashing yes" if you don't have such hard requirements but
  1276. # want to free memory asap when possible.
  1277. activerehashing yes
  1278. # The client output buffer limits can be used to force disconnection of clients
  1279. # that are not reading data from the server fast enough for some reason (a
  1280. # common reason is that a Pub/Sub client can't consume messages as fast as the
  1281. # publisher can produce them).
  1282. #
  1283. # The limit can be set differently for the three different classes of clients:
  1284. #
  1285. # normal -> normal clients including MONITOR clients
  1286. # replica -> replica clients
  1287. # pubsub -> clients subscribed to at least one pubsub channel or pattern
  1288. #
  1289. # The syntax of every client-output-buffer-limit directive is the following:
  1290. #
  1291. # client-output-buffer-limit <class> <hard limit> <soft limit> <soft seconds>
  1292. #
  1293. # A client is immediately disconnected once the hard limit is reached, or if
  1294. # the soft limit is reached and remains reached for the specified number of
  1295. # seconds (continuously).
  1296. # So for instance if the hard limit is 32 megabytes and the soft limit is
  1297. # 16 megabytes / 10 seconds, the client will get disconnected immediately
  1298. # if the size of the output buffers reach 32 megabytes, but will also get
  1299. # disconnected if the client reaches 16 megabytes and continuously overcomes
  1300. # the limit for 10 seconds.
  1301. #
  1302. # By default normal clients are not limited because they don't receive data
  1303. # without asking (in a push way), but just after a request, so only
  1304. # asynchronous clients may create a scenario where data is requested faster
  1305. # than it can read.
  1306. #
  1307. # Instead there is a default limit for pubsub and replica clients, since
  1308. # subscribers and replicas receive data in a push fashion.
  1309. #
  1310. # Both the hard or the soft limit can be disabled by setting them to zero.
  1311. client-output-buffer-limit normal 0 0 0
  1312. client-output-buffer-limit replica 256mb 64mb 60
  1313. client-output-buffer-limit pubsub 32mb 8mb 60
  1314. # Client query buffers accumulate new commands. They are limited to a fixed
  1315. # amount by default in order to avoid that a protocol desynchronization (for
  1316. # instance due to a bug in the client) will lead to unbound memory usage in
  1317. # the query buffer. However you can configure it here if you have very special
  1318. # needs, such us huge multi/exec requests or alike.
  1319. #
  1320. # client-query-buffer-limit 1gb
  1321. # In the Redis protocol, bulk requests, that are, elements representing single
  1322. # strings, are normally limited ot 512 mb. However you can change this limit
  1323. # here.
  1324. #
  1325. # proto-max-bulk-len 512mb
  1326. # Redis calls an internal function to perform many background tasks, like
  1327. # closing connections of clients in timeout, purging expired keys that are
  1328. # never requested, and so forth.
  1329. #
  1330. # Not all tasks are performed with the same frequency, but Redis checks for
  1331. # tasks to perform according to the specified "hz" value.
  1332. #
  1333. # By default "hz" is set to 10. Raising the value will use more CPU when
  1334. # Redis is idle, but at the same time will make Redis more responsive when
  1335. # there are many keys expiring at the same time, and timeouts may be
  1336. # handled with more precision.
  1337. #
  1338. # The range is between 1 and 500, however a value over 100 is usually not
  1339. # a good idea. Most users should use the default of 10 and raise this up to
  1340. # 100 only in environments where very low latency is required.
  1341. hz 10
  1342. # Normally it is useful to have an HZ value which is proportional to the
  1343. # number of clients connected. This is useful in order, for instance, to
  1344. # avoid too many clients are processed for each background task invocation
  1345. # in order to avoid latency spikes.
  1346. #
  1347. # Since the default HZ value by default is conservatively set to 10, Redis
  1348. # offers, and enables by default, the ability to use an adaptive HZ value
  1349. # which will temporary raise when there are many connected clients.
  1350. #
  1351. # When dynamic HZ is enabled, the actual configured HZ will be used as
  1352. # as a baseline, but multiples of the configured HZ value will be actually
  1353. # used as needed once more clients are connected. In this way an idle
  1354. # instance will use very little CPU time while a busy instance will be
  1355. # more responsive.
  1356. dynamic-hz yes
  1357. # When a child rewrites the AOF file, if the following option is enabled
  1358. # the file will be fsync-ed every 32 MB of data generated. This is useful
  1359. # in order to commit the file to the disk more incrementally and avoid
  1360. # big latency spikes.
  1361. aof-rewrite-incremental-fsync yes
  1362. # When redis saves RDB file, if the following option is enabled
  1363. # the file will be fsync-ed every 32 MB of data generated. This is useful
  1364. # in order to commit the file to the disk more incrementally and avoid
  1365. # big latency spikes.
  1366. rdb-save-incremental-fsync yes
  1367. # Redis LFU eviction (see maxmemory setting) can be tuned. However it is a good
  1368. # idea to start with the default settings and only change them after investigating
  1369. # how to improve the performances and how the keys LFU change over time, which
  1370. # is possible to inspect via the OBJECT FREQ command.
  1371. #
  1372. # There are two tunable parameters in the Redis LFU implementation: the
  1373. # counter logarithm factor and the counter decay time. It is important to
  1374. # understand what the two parameters mean before changing them.
  1375. #
  1376. # The LFU counter is just 8 bits per key, it's maximum value is 255, so Redis
  1377. # uses a probabilistic increment with logarithmic behavior. Given the value
  1378. # of the old counter, when a key is accessed, the counter is incremented in
  1379. # this way:
  1380. #
  1381. # 1. A random number R between 0 and 1 is extracted.
  1382. # 2. A probability P is calculated as 1/(old_value*lfu_log_factor+1).
  1383. # 3. The counter is incremented only if R < P.
  1384. #
  1385. # The default lfu-log-factor is 10. This is a table of how the frequency
  1386. # counter changes with a different number of accesses with different
  1387. # logarithmic factors:
  1388. #
  1389. # +--------+------------+------------+------------+------------+------------+
  1390. # | factor | 100 hits | 1000 hits | 100K hits | 1M hits | 10M hits |
  1391. # +--------+------------+------------+------------+------------+------------+
  1392. # | 0 | 104 | 255 | 255 | 255 | 255 |
  1393. # +--------+------------+------------+------------+------------+------------+
  1394. # | 1 | 18 | 49 | 255 | 255 | 255 |
  1395. # +--------+------------+------------+------------+------------+------------+
  1396. # | 10 | 10 | 18 | 142 | 255 | 255 |
  1397. # +--------+------------+------------+------------+------------+------------+
  1398. # | 100 | 8 | 11 | 49 | 143 | 255 |
  1399. # +--------+------------+------------+------------+------------+------------+
  1400. #
  1401. # NOTE: The above table was obtained by running the following commands:
  1402. #
  1403. # redis-benchmark -n 1000000 incr foo
  1404. # redis-cli object freq foo
  1405. #
  1406. # NOTE 2: The counter initial value is 5 in order to give new objects a chance
  1407. # to accumulate hits.
  1408. #
  1409. # The counter decay time is the time, in minutes, that must elapse in order
  1410. # for the key counter to be divided by two (or decremented if it has a value
  1411. # less <= 10).
  1412. #
  1413. # The default value for the lfu-decay-time is 1. A Special value of 0 means to
  1414. # decay the counter every time it happens to be scanned.
  1415. #
  1416. # lfu-log-factor 10
  1417. # lfu-decay-time 1
  1418. ########################### ACTIVE DEFRAGMENTATION #######################
  1419. #
  1420. # WARNING THIS FEATURE IS EXPERIMENTAL. However it was stress tested
  1421. # even in production and manually tested by multiple engineers for some
  1422. # time.
  1423. #
  1424. # What is active defragmentation?
  1425. # -------------------------------
  1426. #
  1427. # Active (online) defragmentation allows a Redis server to compact the
  1428. # spaces left between small allocations and deallocations of data in memory,
  1429. # thus allowing to reclaim back memory.
  1430. #
  1431. # Fragmentation is a natural process that happens with every allocator (but
  1432. # less so with Jemalloc, fortunately) and certain workloads. Normally a server
  1433. # restart is needed in order to lower the fragmentation, or at least to flush
  1434. # away all the data and create it again. However thanks to this feature
  1435. # implemented by Oran Agra for Redis 4.0 this process can happen at runtime
  1436. # in an "hot" way, while the server is running.
  1437. #
  1438. # Basically when the fragmentation is over a certain level (see the
  1439. # configuration options below) Redis will start to create new copies of the
  1440. # values in contiguous memory regions by exploiting certain specific Jemalloc
  1441. # features (in order to understand if an allocation is causing fragmentation
  1442. # and to allocate it in a better place), and at the same time, will release the
  1443. # old copies of the data. This process, repeated incrementally for all the keys
  1444. # will cause the fragmentation to drop back to normal values.
  1445. #
  1446. # Important things to understand:
  1447. #
  1448. # 1. This feature is disabled by default, and only works if you compiled Redis
  1449. # to use the copy of Jemalloc we ship with the source code of Redis.
  1450. # This is the default with Linux builds.
  1451. #
  1452. # 2. You never need to enable this feature if you don't have fragmentation
  1453. # issues.
  1454. #
  1455. # 3. Once you experience fragmentation, you can enable this feature when
  1456. # needed with the command "CONFIG SET activedefrag yes".
  1457. #
  1458. # The configuration parameters are able to fine tune the behavior of the
  1459. # defragmentation process. If you are not sure about what they mean it is
  1460. # a good idea to leave the defaults untouched.
  1461. # Enabled active defragmentation
  1462. # activedefrag yes
  1463. # Minimum amount of fragmentation waste to start active defrag
  1464. # active-defrag-ignore-bytes 100mb
  1465. # Minimum percentage of fragmentation to start active defrag
  1466. # active-defrag-threshold-lower 10
  1467. # Maximum percentage of fragmentation at which we use maximum effort
  1468. # active-defrag-threshold-upper 100
  1469. # Minimal effort for defrag in CPU percentage
  1470. # active-defrag-cycle-min 5
  1471. # Maximal effort for defrag in CPU percentage
  1472. # active-defrag-cycle-max 75
  1473. # Maximum number of set/hash/zset/list fields that will be processed from
  1474. # the main dictionary scan
  1475. # active-defrag-max-scan-fields 1000