Guest User

puppet-redis default conf

a guest
Mar 27th, 2014
166
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
  1. # Redis configuration file example
  2.  
  3. # Note on units: when memory size is needed, it is possible to specify
  4. # it in the usual form of 1k 5GB 4M and so forth:
  5. #
  6. # 1k => 1000 bytes
  7. # 1kb => 1024 bytes
  8. # 1m => 1000000 bytes
  9. # 1mb => 1024*1024 bytes
  10. # 1g => 1000000000 bytes
  11. # 1gb => 1024*1024*1024 bytes
  12. #
  13. # units are case insensitive so 1GB 1Gb 1gB are all the same.
  14.  
  15. ################################## INCLUDES ###################################
  16.  
  17. # Include one or more other config files here. This is useful if you
  18. # have a standard template that goes to all Redis server but also need
  19. # to customize a few per-server settings. Include files can include
  20. # other files, so use this wisely.
  21. #
  22. # Notice option "include" won't be rewritten by command "CONFIG REWRITE"
  23. # from admin or Redis Sentinel. Since Redis always uses the last processed
  24. # line as value of a configuration directive, you'd better put includes
  25. # at the beginning of this file to avoid overwriting config change at runtime.
  26. #
  27. # If instead you are interested in using includes to override configuration
  28. # options, it is better to use include as the last line.
  29. #
  30. # include /path/to/local.conf
  31. # include /path/to/other.conf
  32.  
  33. ################################ GENERAL #####################################
  34.  
  35. # By default Redis does not run as a daemon. Use 'yes' if you need it.
  36. # Note that Redis will write a pid file in /var/run/redis.pid when daemonized.
  37. daemonize yes
  38.  
  39. # When running daemonized, Redis writes a pid file in /var/run/redis.pid by
  40. # default. You can specify a custom pid file location here.
  41. pidfile /var/run/redis_6379.pid
  42.  
  43. # Accept connections on the specified port, default is 6379.
  44. # If port 0 is specified Redis will not listen on a TCP socket.
  45. port 6379
  46.  
  47. # TCP listen() backlog.
  48. #
  49. # In high requests-per-second environments you need an high backlog in order
  50. # to avoid slow clients connections issues. Note that the Linux kernel
  51. # will silently truncate it to the value of /proc/sys/net/core/somaxconn so
  52. # make sure to raise both the value of somaxconn and tcp_max_syn_backlog
  53. # in order to get the desired effect.
  54. tcp-backlog 511
  55.  
  56. # By default Redis listens for connections from all the network interfaces
  57. # available on the server. It is possible to listen to just one or multiple
  58. # interfaces using the "bind" configuration directive, followed by one or
  59. # more IP addresses.
  60. #
  61. # Examples:
  62. #
  63. # bind 192.168.1.100 10.0.0.1
  64. # bind 127.0.0.1
  65.  
  66. # Specify the path for the Unix socket that will be used to listen for
  67. # incoming connections. There is no default, so Redis will not listen
  68. # on a unix socket when not specified.
  69. #
  70. # unixsocket /tmp/redis.sock
  71. # unixsocketperm 755
  72.  
  73. # Close the connection after a client is idle for N seconds (0 to disable)
  74. timeout 0
  75.  
  76. # TCP keepalive.
  77. #
  78. # If non-zero, use SO_KEEPALIVE to send TCP ACKs to clients in absence
  79. # of communication. This is useful for two reasons:
  80. #
  81. # 1) Detect dead peers.
  82. # 2) Take the connection alive from the point of view of network
  83. # equipment in the middle.
  84. #
  85. # On Linux, the specified value (in seconds) is the period used to send ACKs.
  86. # Note that to close the connection the double of the time is needed.
  87. # On other kernels the period depends on the kernel configuration.
  88. #
  89. # A reasonable value for this option is 60 seconds.
  90. tcp-keepalive 0
  91.  
  92. # Specify the server verbosity level.
  93. # This can be one of:
  94. # debug (a lot of information, useful for development/testing)
  95. # verbose (many rarely useful info, but not a mess like the debug level)
  96. # notice (moderately verbose, what you want in production probably)
  97. # warning (only very important / critical messages are logged)
  98. loglevel notice
  99.  
  100. # Specify the log file name. Also the empty string can be used to force
  101. # Redis to log on the standard output. Note that if you use standard
  102. # output for logging but daemonize, logs will be sent to /dev/null
  103. logfile /var/log/redis_6379.log
  104.  
  105. # To enable logging to the system logger, just set 'syslog-enabled' to yes,
  106. # and optionally update the other syslog parameters to suit your needs.
  107. # syslog-enabled no
  108.  
  109. # Specify the syslog identity.
  110. # syslog-ident redis
  111.  
  112. # Specify the syslog facility. Must be USER or between LOCAL0-LOCAL7.
  113. # syslog-facility local0
  114.  
  115. # Set the number of databases. The default database is DB 0, you can select
  116. # a different one on a per-connection basis using SELECT <dbid> where
  117. # dbid is a number between 0 and 'databases'-1
  118. databases 16
  119.  
  120. ################################ SNAPSHOTTING ################################
  121. #
  122. # Save the DB on disk:
  123. #
  124. # save <seconds> <changes>
  125. #
  126. # Will save the DB if both the given number of seconds and the given
  127. # number of write operations against the DB occurred.
  128. #
  129. # In the example below the behaviour will be to save:
  130. # after 900 sec (15 min) if at least 1 key changed
  131. # after 300 sec (5 min) if at least 10 keys changed
  132. # after 60 sec if at least 10000 keys changed
  133. #
  134. # Note: you can disable saving at all commenting all the "save" lines.
  135. #
  136. # It is also possible to remove all the previously configured save
  137. # points by adding a save directive with a single empty string argument
  138. # like in the following example:
  139. #
  140. # save ""
  141.  
  142. save 900 1
  143. save 300 10
  144. save 60 10000
  145.  
  146. # By default Redis will stop accepting writes if RDB snapshots are enabled
  147. # (at least one save point) and the latest background save failed.
  148. # This will make the user aware (in a hard way) that data is not persisting
  149. # on disk properly, otherwise chances are that no one will notice and some
  150. # disaster will happen.
  151. #
  152. # If the background saving process will start working again Redis will
  153. # automatically allow writes again.
  154. #
  155. # However if you have setup your proper monitoring of the Redis server
  156. # and persistence, you may want to disable this feature so that Redis will
  157. # continue to work as usual even if there are problems with disk,
  158. # permissions, and so forth.
  159. stop-writes-on-bgsave-error yes
  160.  
  161. # Compress string objects using LZF when dump .rdb databases?
  162. # For default that's set to 'yes' as it's almost always a win.
  163. # If you want to save some CPU in the saving child set it to 'no' but
  164. # the dataset will likely be bigger if you have compressible values or keys.
  165. rdbcompression yes
  166.  
  167. # Since version 5 of RDB a CRC64 checksum is placed at the end of the file.
  168. # This makes the format more resistant to corruption but there is a performance
  169. # hit to pay (around 10%) when saving and loading RDB files, so you can disable it
  170. # for maximum performances.
  171. #
  172. # RDB files created with checksum disabled have a checksum of zero that will
  173. # tell the loading code to skip the check.
  174. rdbchecksum yes
  175.  
  176. # The filename where to dump the DB
  177. dbfilename dump.rdb
  178.  
  179. # The working directory.
  180. #
  181. # The DB will be written inside this directory, with the filename specified
  182. # above using the 'dbfilename' configuration directive.
  183. #
  184. # The Append Only File will also be created inside this directory.
  185. #
  186. # Note that you must specify a directory here, not a file name.
  187. dir /var/lib/redis/6379
  188.  
  189. ################################# REPLICATION #################################
  190.  
  191. # Master-Slave replication. Use slaveof to make a Redis instance a copy of
  192. # another Redis server. Note that the configuration is local to the slave
  193. # so for example it is possible to configure the slave to save the DB with a
  194. # different interval, or to listen to another port, and so on.
  195. #
  196. # slaveof <masterip> <masterport>
  197.  
  198. # If the master is password protected (using the "requirepass" configuration
  199. # directive below) it is possible to tell the slave to authenticate before
  200. # starting the replication synchronization process, otherwise the master will
  201. # refuse the slave request.
  202. #
  203. # masterauth <master-password>
  204.  
  205. # When a slave loses its connection with the master, or when the replication
  206. # is still in progress, the slave can act in two different ways:
  207. #
  208. # 1) if slave-serve-stale-data is set to 'yes' (the default) the slave will
  209. # still reply to client requests, possibly with out of date data, or the
  210. # data set may just be empty if this is the first synchronization.
  211. #
  212. # 2) if slave-serve-stale-data is set to 'no' the slave will reply with
  213. # an error "SYNC with master in progress" to all the kind of commands
  214. # but to INFO and SLAVEOF.
  215. #
  216. slave-serve-stale-data yes
  217.  
  218. # You can configure a slave instance to accept writes or not. Writing against
  219. # a slave instance may be useful to store some ephemeral data (because data
  220. # written on a slave will be easily deleted after resync with the master) but
  221. # may also cause problems if clients are writing to it because of a
  222. # misconfiguration.
  223. #
  224. # Since Redis 2.6 by default slaves are read-only.
  225. #
  226. # Note: read only slaves are not designed to be exposed to untrusted clients
  227. # on the internet. It's just a protection layer against misuse of the instance.
  228. # Still a read only slave exports by default all the administrative commands
  229. # such as CONFIG, DEBUG, and so forth. To a limited extent you can improve
  230. # security of read only slaves using 'rename-command' to shadow all the
  231. # administrative / dangerous commands.
  232. slave-read-only yes
  233.  
  234. # Slaves send PINGs to server in a predefined interval. It's possible to change
  235. # this interval with the repl_ping_slave_period option. The default value is 10
  236. # seconds.
  237. #
  238. # repl-ping-slave-period 10
  239.  
  240. # The following option sets the replication timeout for:
  241. #
  242. # 1) Bulk transfer I/O during SYNC, from the point of view of slave.
  243. # 2) Master timeout from the point of view of slaves (data, pings).
  244. # 3) Slave timeout from the point of view of masters (REPLCONF ACK pings).
  245. #
  246. # It is important to make sure that this value is greater than the value
  247. # specified for repl-ping-slave-period otherwise a timeout will be detected
  248. # every time there is low traffic between the master and the slave.
  249. #
  250. # repl-timeout 60
  251.  
  252. # Disable TCP_NODELAY on the slave socket after SYNC?
  253. #
  254. # If you select "yes" Redis will use a smaller number of TCP packets and
  255. # less bandwidth to send data to slaves. But this can add a delay for
  256. # the data to appear on the slave side, up to 40 milliseconds with
  257. # Linux kernels using a default configuration.
  258. #
  259. # If you select "no" the delay for data to appear on the slave side will
  260. # be reduced but more bandwidth will be used for replication.
  261. #
  262. # By default we optimize for low latency, but in very high traffic conditions
  263. # or when the master and slaves are many hops away, turning this to "yes" may
  264. # be a good idea.
  265. repl-disable-tcp-nodelay no
  266.  
  267. # Set the replication backlog size. The backlog is a buffer that accumulates
  268. # slave data when slaves are disconnected for some time, so that when a slave
  269. # wants to reconnect again, often a full resync is not needed, but a partial
  270. # resync is enough, just passing the portion of data the slave missed while
  271. # disconnected.
  272. #
  273. # The biggest the replication backlog, the longer the time the slave can be
  274. # disconnected and later be able to perform a partial resynchronization.
  275. #
  276. # The backlog is only allocated once there is at least a slave connected.
  277. #
  278. # repl-backlog-size 1mb
  279.  
  280. # After a master has no longer connected slaves for some time, the backlog
  281. # will be freed. The following option configures the amount of seconds that
  282. # need to elapse, starting from the time the last slave disconnected, for
  283. # the backlog buffer to be freed.
  284. #
  285. # A value of 0 means to never release the backlog.
  286. #
  287. # repl-backlog-ttl 3600
  288.  
  289. # The slave priority is an integer number published by Redis in the INFO output.
  290. # It is used by Redis Sentinel in order to select a slave to promote into a
  291. # master if the master is no longer working correctly.
  292. #
  293. # A slave with a low priority number is considered better for promotion, so
  294. # for instance if there are three slaves with priority 10, 100, 25 Sentinel will
  295. # pick the one with priority 10, that is the lowest.
  296. #
  297. # However a special priority of 0 marks the slave as not able to perform the
  298. # role of master, so a slave with priority of 0 will never be selected by
  299. # Redis Sentinel for promotion.
  300. #
  301. # By default the priority is 100.
  302. slave-priority 100
  303.  
  304. # It is possible for a master to stop accepting writes if there are less than
  305. # N slaves connected, having a lag less or equal than M seconds.
  306. #
  307. # The N slaves need to be in "online" state.
  308. #
  309. # The lag in seconds, that must be <= the specified value, is calculated from
  310. # the last ping received from the slave, that is usually sent every second.
  311. #
  312. # This option does not GUARANTEES that N replicas will accept the write, but
  313. # will limit the window of exposure for lost writes in case not enough slaves
  314. # are available, to the specified number of seconds.
  315. #
  316. # For example to require at least 3 slaves with a lag <= 10 seconds use:
  317. #
  318. # min-slaves-to-write 3
  319. # min-slaves-max-lag 10
  320. #
  321. # Setting one or the other to 0 disables the feature.
  322. #
  323. # By default min-slaves-to-write is set to 0 (feature disabled) and
  324. # min-slaves-max-lag is set to 10.
  325.  
  326. ################################## SECURITY ###################################
  327.  
  328. # Require clients to issue AUTH <PASSWORD> before processing any other
  329. # commands. This might be useful in environments in which you do not trust
  330. # others with access to the host running redis-server.
  331. #
  332. # This should stay commented out for backward compatibility and because most
  333. # people do not need auth (e.g. they run their own servers).
  334. #
  335. # Warning: since Redis is pretty fast an outside user can try up to
  336. # 150k passwords per second against a good box. This means that you should
  337. # use a very strong password otherwise it will be very easy to break.
  338. #
  339. # requirepass foobared
  340.  
  341. # Command renaming.
  342. #
  343. # It is possible to change the name of dangerous commands in a shared
  344. # environment. For instance the CONFIG command may be renamed into something
  345. # hard to guess so that it will still be available for internal-use tools
  346. # but not available for general clients.
  347. #
  348. # Example:
  349. #
  350. # rename-command CONFIG b840fc02d524045429941cc15f59e41cb7be6c52
  351. #
  352. # It is also possible to completely kill a command by renaming it into
  353. # an empty string:
  354. #
  355. # rename-command CONFIG ""
  356. #
  357. # Please note that changing the name of commands that are logged into the
  358. # AOF file or transmitted to slaves may cause problems.
  359.  
  360. ################################### LIMITS ####################################
  361.  
  362. # Set the max number of connected clients at the same time. By default
  363. # this limit is set to 10000 clients, however if the Redis server is not
  364. # able to configure the process file limit to allow for the specified limit
  365. # the max number of allowed clients is set to the current file limit
  366. # minus 32 (as Redis reserves a few file descriptors for internal uses).
  367. #
  368. # Once the limit is reached Redis will close all the new connections sending
  369. # an error 'max number of clients reached'.
  370. #
  371. # maxclients 10000
  372.  
  373. # Don't use more memory than the specified amount of bytes.
  374. # When the memory limit is reached Redis will try to remove keys
  375. # according to the eviction policy selected (see maxmemory-policy).
  376. #
  377. # If Redis can't remove keys according to the policy, or if the policy is
  378. # set to 'noeviction', Redis will start to reply with errors to commands
  379. # that would use more memory, like SET, LPUSH, and so on, and will continue
  380. # to reply to read-only commands like GET.
  381. #
  382. # This option is usually useful when using Redis as an LRU cache, or to set
  383. # a hard memory limit for an instance (using the 'noeviction' policy).
  384. #
  385. # WARNING: If you have slaves attached to an instance with maxmemory on,
  386. # the size of the output buffers needed to feed the slaves are subtracted
  387. # from the used memory count, so that network problems / resyncs will
  388. # not trigger a loop where keys are evicted, and in turn the output
  389. # buffer of slaves is full with DELs of keys evicted triggering the deletion
  390. # of more keys, and so forth until the database is completely emptied.
  391. #
  392. # In short... if you have slaves attached it is suggested that you set a lower
  393. # limit for maxmemory so that there is some free RAM on the system for slave
  394. # output buffers (but this is not needed if the policy is 'noeviction').
  395. #
  396. # maxmemory <bytes>
  397.  
  398. # MAXMEMORY POLICY: how Redis will select what to remove when maxmemory
  399. # is reached. You can select among five behaviors:
  400. #
  401. # volatile-lru -> remove the key with an expire set using an LRU algorithm
  402. # allkeys-lru -> remove any key accordingly to the LRU algorithm
  403. # volatile-random -> remove a random key with an expire set
  404. # allkeys-random -> remove a random key, any key
  405. # volatile-ttl -> remove the key with the nearest expire time (minor TTL)
  406. # noeviction -> don't expire at all, just return an error on write operations
  407. #
  408. # Note: with any of the above policies, Redis will return an error on write
  409. # operations, when there are not suitable keys for eviction.
  410. #
  411. # At the date of writing this commands are: set setnx setex append
  412. # incr decr rpush lpush rpushx lpushx linsert lset rpoplpush sadd
  413. # sinter sinterstore sunion sunionstore sdiff sdiffstore zadd zincrby
  414. # zunionstore zinterstore hset hsetnx hmset hincrby incrby decrby
  415. # getset mset msetnx exec sort
  416. #
  417. # The default is:
  418. #
  419. # maxmemory-policy volatile-lru
  420.  
  421. # LRU and minimal TTL algorithms are not precise algorithms but approximated
  422. # algorithms (in order to save memory), so you can select as well the sample
  423. # size to check. For instance for default Redis will check three keys and
  424. # pick the one that was used less recently, you can change the sample size
  425. # using the following configuration directive.
  426. #
  427. # maxmemory-samples 3
  428.  
  429. ############################## APPEND ONLY MODE ###############################
  430.  
  431. # By default Redis asynchronously dumps the dataset on disk. This mode is
  432. # good enough in many applications, but an issue with the Redis process or
  433. # a power outage may result into a few minutes of writes lost (depending on
  434. # the configured save points).
  435. #
  436. # The Append Only File is an alternative persistence mode that provides
  437. # much better durability. For instance using the default data fsync policy
  438. # (see later in the config file) Redis can lose just one second of writes in a
  439. # dramatic event like a server power outage, or a single write if something
  440. # wrong with the Redis process itself happens, but the operating system is
  441. # still running correctly.
  442. #
  443. # AOF and RDB persistence can be enabled at the same time without problems.
  444. # If the AOF is enabled on startup Redis will load the AOF, that is the file
  445. # with the better durability guarantees.
  446. #
  447. # Please check http://redis.io/topics/persistence for more information.
  448.  
  449. appendonly no
  450.  
  451. # The name of the append only file (default: "appendonly.aof")
  452.  
  453. appendfilename "appendonly.aof"
  454.  
  455. # The fsync() call tells the Operating System to actually write data on disk
  456. # instead to wait for more data in the output buffer. Some OS will really flush
  457. # data on disk, some other OS will just try to do it ASAP.
  458. #
  459. # Redis supports three different modes:
  460. #
  461. # no: don't fsync, just let the OS flush the data when it wants. Faster.
  462. # always: fsync after every write to the append only log . Slow, Safest.
  463. # everysec: fsync only one time every second. Compromise.
  464. #
  465. # The default is "everysec", as that's usually the right compromise between
  466. # speed and data safety. It's up to you to understand if you can relax this to
  467. # "no" that will let the operating system flush the output buffer when
  468. # it wants, for better performances (but if you can live with the idea of
  469. # some data loss consider the default persistence mode that's snapshotting),
  470. # or on the contrary, use "always" that's very slow but a bit safer than
  471. # everysec.
  472. #
  473. # More details please check the following article:
  474. # http://antirez.com/post/redis-persistence-demystified.html
  475. #
  476. # If unsure, use "everysec".
  477.  
  478. # appendfsync always
  479. appendfsync everysec
  480. # appendfsync no
  481.  
  482. # When the AOF fsync policy is set to always or everysec, and a background
  483. # saving process (a background save or AOF log background rewriting) is
  484. # performing a lot of I/O against the disk, in some Linux configurations
  485. # Redis may block too long on the fsync() call. Note that there is no fix for
  486. # this currently, as even performing fsync in a different thread will block
  487. # our synchronous write(2) call.
  488. #
  489. # In order to mitigate this problem it's possible to use the following option
  490. # that will prevent fsync() from being called in the main process while a
  491. # BGSAVE or BGREWRITEAOF is in progress.
  492. #
  493. # This means that while another child is saving, the durability of Redis is
  494. # the same as "appendfsync none". In practical terms, this means that it is
  495. # possible to lose up to 30 seconds of log in the worst scenario (with the
  496. # default Linux settings).
  497. #
  498. # If you have latency problems turn this to "yes". Otherwise leave it as
  499. # "no" that is the safest pick from the point of view of durability.
  500.  
  501. no-appendfsync-on-rewrite no
  502.  
  503. # Automatic rewrite of the append only file.
  504. # Redis is able to automatically rewrite the log file implicitly calling
  505. # BGREWRITEAOF when the AOF log size grows by the specified percentage.
  506. #
  507. # This is how it works: Redis remembers the size of the AOF file after the
  508. # latest rewrite (if no rewrite has happened since the restart, the size of
  509. # the AOF at startup is used).
  510. #
  511. # This base size is compared to the current size. If the current size is
  512. # bigger than the specified percentage, the rewrite is triggered. Also
  513. # you need to specify a minimal size for the AOF file to be rewritten, this
  514. # is useful to avoid rewriting the AOF file even if the percentage increase
  515. # is reached but it is still pretty small.
  516. #
  517. # Specify a percentage of zero in order to disable the automatic AOF
  518. # rewrite feature.
  519.  
  520. auto-aof-rewrite-percentage 100
  521. auto-aof-rewrite-min-size 64mb
  522.  
  523. ################################ LUA SCRIPTING ###############################
  524.  
  525. # Max execution time of a Lua script in milliseconds.
  526. #
  527. # If the maximum execution time is reached Redis will log that a script is
  528. # still in execution after the maximum allowed time and will start to
  529. # reply to queries with an error.
  530. #
  531. # When a long running script exceed the maximum execution time only the
  532. # SCRIPT KILL and SHUTDOWN NOSAVE commands are available. The first can be
  533. # used to stop a script that did not yet called write commands. The second
  534. # is the only way to shut down the server in the case a write commands was
  535. # already issue by the script but the user don't want to wait for the natural
  536. # termination of the script.
  537. #
  538. # Set it to 0 or a negative value for unlimited execution without warnings.
  539. lua-time-limit 5000
  540.  
  541. ################################## SLOW LOG ###################################
  542.  
  543. # The Redis Slow Log is a system to log queries that exceeded a specified
  544. # execution time. The execution time does not include the I/O operations
  545. # like talking with the client, sending the reply and so forth,
  546. # but just the time needed to actually execute the command (this is the only
  547. # stage of command execution where the thread is blocked and can not serve
  548. # other requests in the meantime).
  549. #
  550. # You can configure the slow log with two parameters: one tells Redis
  551. # what is the execution time, in microseconds, to exceed in order for the
  552. # command to get logged, and the other parameter is the length of the
  553. # slow log. When a new command is logged the oldest one is removed from the
  554. # queue of logged commands.
  555.  
  556. # The following time is expressed in microseconds, so 1000000 is equivalent
  557. # to one second. Note that a negative number disables the slow log, while
  558. # a value of zero forces the logging of every command.
  559. slowlog-log-slower-than 10000
  560.  
  561. # There is no limit to this length. Just be aware that it will consume memory.
  562. # You can reclaim memory used by the slow log with SLOWLOG RESET.
  563. slowlog-max-len 128
  564.  
  565. ############################# Event notification ##############################
  566.  
  567. # Redis can notify Pub/Sub clients about events happening in the key space.
  568. # This feature is documented at http://redis.io/topics/keyspace-events
  569. #
  570. # For instance if keyspace events notification is enabled, and a client
  571. # performs a DEL operation on key "foo" stored in the Database 0, two
  572. # messages will be published via Pub/Sub:
  573. #
  574. # PUBLISH __keyspace@0__:foo del
  575. # PUBLISH __keyevent@0__:del foo
  576. #
  577. # It is possible to select the events that Redis will notify among a set
  578. # of classes. Every class is identified by a single character:
  579. #
  580. # K Keyspace events, published with __keyspace@<db>__ prefix.
  581. # E Keyevent events, published with __keyevent@<db>__ prefix.
  582. # g Generic commands (non-type specific) like DEL, EXPIRE, RENAME, ...
  583. # $ String commands
  584. # l List commands
  585. # s Set commands
  586. # h Hash commands
  587. # z Sorted set commands
  588. # x Expired events (events generated every time a key expires)
  589. # e Evicted events (events generated when a key is evicted for maxmemory)
  590. # A Alias for g$lshzxe, so that the "AKE" string means all the events.
  591. #
  592. # The "notify-keyspace-events" takes as argument a string that is composed
  593. # by zero or multiple characters. The empty string means that notifications
  594. # are disabled at all.
  595. #
  596. # Example: to enable list and generic events, from the point of view of the
  597. # event name, use:
  598. #
  599. # notify-keyspace-events Elg
  600. #
  601. # Example 2: to get the stream of the expired keys subscribing to channel
  602. # name __keyevent@0__:expired use:
  603. #
  604. # notify-keyspace-events Ex
  605. #
  606. # By default all notifications are disabled because most users don't need
  607. # this feature and the feature has some overhead. Note that if you don't
  608. # specify at least one of K or E, no events will be delivered.
  609. notify-keyspace-events ""
  610.  
  611. ############################### ADVANCED CONFIG ###############################
  612.  
  613. # Hashes are encoded using a memory efficient data structure when they have a
  614. # small number of entries, and the biggest entry does not exceed a given
  615. # threshold. These thresholds can be configured using the following directives.
  616. hash-max-ziplist-entries 512
  617. hash-max-ziplist-value 64
  618.  
  619. # Similarly to hashes, small lists are also encoded in a special way in order
  620. # to save a lot of space. The special representation is only used when
  621. # you are under the following limits:
  622. list-max-ziplist-entries 512
  623. list-max-ziplist-value 64
  624.  
  625. # Sets have a special encoding in just one case: when a set is composed
  626. # of just strings that happens to be integers in radix 10 in the range
  627. # of 64 bit signed integers.
  628. # The following configuration setting sets the limit in the size of the
  629. # set in order to use this special memory saving encoding.
  630. set-max-intset-entries 512
  631.  
  632. # Similarly to hashes and lists, sorted sets are also specially encoded in
  633. # order to save a lot of space. This encoding is only used when the length and
  634. # elements of a sorted set are below the following limits:
  635. zset-max-ziplist-entries 128
  636. zset-max-ziplist-value 64
  637.  
  638. # Active rehashing uses 1 millisecond every 100 milliseconds of CPU time in
  639. # order to help rehashing the main Redis hash table (the one mapping top-level
  640. # keys to values). The hash table implementation Redis uses (see dict.c)
  641. # performs a lazy rehashing: the more operation you run into a hash table
  642. # that is rehashing, the more rehashing "steps" are performed, so if the
  643. # server is idle the rehashing is never complete and some more memory is used
  644. # by the hash table.
  645. #
  646. # The default is to use this millisecond 10 times every second in order to
  647. # active rehashing the main dictionaries, freeing memory when possible.
  648. #
  649. # If unsure:
  650. # use "activerehashing no" if you have hard latency requirements and it is
  651. # not a good thing in your environment that Redis can reply form time to time
  652. # to queries with 2 milliseconds delay.
  653. #
  654. # use "activerehashing yes" if you don't have such hard requirements but
  655. # want to free memory asap when possible.
  656. activerehashing yes
  657.  
  658. # The client output buffer limits can be used to force disconnection of clients
  659. # that are not reading data from the server fast enough for some reason (a
  660. # common reason is that a Pub/Sub client can't consume messages as fast as the
  661. # publisher can produce them).
  662. #
  663. # The limit can be set differently for the three different classes of clients:
  664. #
  665. # normal -> normal clients
  666. # slave -> slave clients and MONITOR clients
  667. # pubsub -> clients subscribed to at least one pubsub channel or pattern
  668. #
  669. # The syntax of every client-output-buffer-limit directive is the following:
  670. #
  671. # client-output-buffer-limit <class> <hard limit> <soft limit> <soft seconds>
  672. #
  673. # A client is immediately disconnected once the hard limit is reached, or if
  674. # the soft limit is reached and remains reached for the specified number of
  675. # seconds (continuously).
  676. # So for instance if the hard limit is 32 megabytes and the soft limit is
  677. # 16 megabytes / 10 seconds, the client will get disconnected immediately
  678. # if the size of the output buffers reach 32 megabytes, but will also get
  679. # disconnected if the client reaches 16 megabytes and continuously overcomes
  680. # the limit for 10 seconds.
  681. #
  682. # By default normal clients are not limited because they don't receive data
  683. # without asking (in a push way), but just after a request, so only
  684. # asynchronous clients may create a scenario where data is requested faster
  685. # than it can read.
  686. #
  687. # Instead there is a default limit for pubsub and slave clients, since
  688. # subscribers and slaves receive data in a push fashion.
  689. #
  690. # Both the hard or the soft limit can be disabled by setting them to zero.
  691. client-output-buffer-limit normal 0 0 0
  692. client-output-buffer-limit slave 256mb 64mb 60
  693. client-output-buffer-limit pubsub 32mb 8mb 60
  694.  
  695. # Redis calls an internal function to perform many background tasks, like
  696. # closing connections of clients in timeout, purging expired keys that are
  697. # never requested, and so forth.
  698. #
  699. # Not all tasks are performed with the same frequency, but Redis checks for
  700. # tasks to perform accordingly to the specified "hz" value.
  701. #
  702. # By default "hz" is set to 10. Raising the value will use more CPU when
  703. # Redis is idle, but at the same time will make Redis more responsive when
  704. # there are many keys expiring at the same time, and timeouts may be
  705. # handled with more precision.
  706. #
  707. # The range is between 1 and 500, however a value over 100 is usually not
  708. # a good idea. Most users should use the default of 10 and raise this up to
  709. # 100 only in environments where very low latency is required.
  710. hz 10
  711.  
  712. # When a child rewrites the AOF file, if the following option is enabled
  713. # the file will be fsync-ed every 32 MB of data generated. This is useful
  714. # in order to commit the file to the disk more incrementally and avoid
  715. # big latency spikes.
  716. aof-rewrite-incremental-fsync yes
RAW Paste Data

Adblocker detected! Please consider disabling it...

We've detected AdBlock Plus or some other adblocking software preventing Pastebin.com from fully loading.

We don't have any obnoxious sound, or popup ads, we actively block these annoying types of ads!

Please add Pastebin.com to your ad blocker whitelist or disable your adblocking software.

×