summaryrefslogtreecommitdiff
path: root/redis.conf
Commit message (Collapse)AuthorAgeFilesLines
* Change unixsocketperm comment to 700 from 755Edgars Irmejs2014-08-071-1/+1
| | | | | | | | According to unix manuals, "Connecting to the socket object requires read/write permission." -- mode 755 is useless for anybody other than the owner. Fixes #1696
* * fixed doc URL for keyspace eventsvps2014-07-281-1/+1
|
* Example redis.conf: improve slaveof description.antirez2014-07-251-3/+12
|
* Latency monitor trheshold value is now configurable.antirez2014-07-021-0/+21
| | | | This commit adds both support for redis.conf and CONFIG SET/GET.
* Client types generalized.antirez2014-06-161-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | Because of output buffer limits Redis internals had this idea of type of clients: normal, pubsub, slave. It is possible to set different output buffer limits for the three kinds of clients. However all the macros and API were named after output buffer limit classes, while the idea of a client type is a generic one that can be reused. This commit does two things: 1) Rename the API and defines with more general names. 2) Change the class of clients executing the MONITOR command from "slave" to "normal". "2" is a good idea because you want to have very special settings for slaves, that are not a good idea for MONITOR clients that are instead normal clients even if they are conceptually slave-alike (since it is a push protocol). The backward-compatibility breakage resulting from "2" is considered to be minimal to care, since MONITOR is a debugging command, and because anyway this change is not going to break the format or the behavior, but just when a connection is closed on big output buffer issues.
* Cluster: slave validity factor is now user configurable.antirez2014-05-221-0/+45
| | | | Check the commit changes in the example redis.conf for more information.
* Fixed typos.Kevin Menard2014-04-231-2/+2
|
* User-defined switch point between sparse-dense HLL encodings.antirez2014-04-151-0/+14
|
* The default maxmemory policy is now noeviction.antirez2014-03-211-1/+1
| | | | | | This is safer as by default maxmemory should just set a memory limit without any key to be deleted, unless the policy is set to something more relaxed.
* Default LRU samples is now 5.antirez2014-03-201-5/+8
|
* Redis.conf comment about tcp-backlog option improved.antirez2014-01-311-1/+7
|
* Option "backlog" renamed "tcp-backlog".antirez2014-01-311-1/+1
| | | | | This is especially important since we already have a concept of backlog (the replication backlog).
* Add support for listen(2) backlog definitionNenad Merdanovic2014-01-311-0/+3
| | | | | | In high RPS environments, the default listen backlog is not sufficient, so giving users the power to configure it is the right approach, especially since it requires only minor modifications to the code.
* Cluster: fix an error in migration-barrier comment in redis.conf.antirez2014-01-311-1/+1
|
* Cluster: barrer -> barrier in redis.conf.antirez2014-01-311-1/+1
|
* Cluster: configurable replicas migration barrier.antirez2014-01-311-0/+19
| | | | | | It is possible to configure the min number of additional working slaves a master should be left with, for a slave to migrate to an orphaned master.
* Clarify include directive behavior in example redis.conf.antirez2013-12-191-2/+6
|
* CONFIG REWRITE: don't throw some options on config rewriteYubao Liu2013-12-191-10/+17
| | | | | | Those options will be thrown without this patch: include, rename-command, min-slaves-to-write, min-slaves-max-lag, appendfilename.
* Example redis.conf formatted to better show appendfilename option.antirez2013-12-191-1/+3
|
* fix typo in redis.conf and sentinel.confYubao Liu2013-12-111-1/+1
|
* Fixed typo in redis.conf.antirez2013-12-061-1/+1
|
* fixed typoAnurag Ramdasan2013-12-051-1/+1
|
* Fixed grammar: 'usually' to 'usual'Anurag Ramdasan2013-12-051-1/+1
|
* Fixed typos in redis.conf file.antirez2013-12-051-8/+8
|
* Cluster: example redis.conf updated from sec to ms for cluster-node-timeout.antirez2013-10-091-3/+3
|
* Revert "Document port6 and bind6 config options."antirez2013-07-081-2/+0
| | | | | | | | | IPv6 support is not going to use IPv6 specific options, just it will be possible to specify all the ipv4 / ipv6 addresses of the interfaces to bind, otherwise connections will be accepted from all the interfaces in both IPv4 and IPv6 addresses. This reverts commit 93570e179e96dc096b85aa0fcd5021b05208594a.
* Document port6 and bind6 config options.Geoff Garside2013-07-081-0/+2
| | | | Add commented port6 and bind6 options to default redis.conf file.
* Example redis.conf: bind to multiple interfaces documented.antirez2013-07-081-2/+7
|
* min-slaves-to-write: don't accept writes with less than N replicas.antirez2013-05-301-1/+7
| | | | | | This feature allows the user to specify the minimum number of connected replicas having a lag less or equal than the specified amount of seconds for writes to be accepted.
* min-slaves-to-write: initial description of the feature in redis.confantirez2013-05-301-0/+16
|
* redis.conf updated: repl-timeout now uesd by masters as well.antirez2013-05-271-2/+5
|
* Added a define for most configuration defaults.antirez2013-05-151-2/+2
| | | | | | | | Also the logfile option was modified to always have an explicit value and to log to stdout when an empty string is used as log file. Previously there was special handling of the string "stdout" that set the logfile to NULL, this always required some special handling.
* Config option to turn AOF rewrite incremental fsync on/off.antirez2013-04-241-0/+6
|
* Cluster: node timeout is now configurable.antirez2013-04-041-0/+6
|
* Add a warning about command renaming in redis.conf.antirez2013-03-061-0/+3
|
* point 2 of slave-serve-stale-data miss '-' between 'stale' and 'data'Stam He2013-03-041-1/+1
|
* PSYNC: work in progress, preview #2, rebased to unstable.antirez2013-02-121-0/+22
|
* TCP keep-alive. Better documentation in redis.conf.antirez2013-02-091-6/+11
|
* tcp-keepalive option documented in redis.conf.antirez2013-02-081-0/+11
|
* TCP_NODELAY after SYNC: changes to the implementation.antirez2013-02-051-0/+15
|
* Fix a few typos and improve grammar of redis.confDavid Celis2013-02-031-20/+20
| | | | | | | Make several edits to the example redis.conf configuration file for improved flow and grammar. Signed-off-by: David Celis <me@davidcel.is>
* Keyspace events: it is now possible to select subclasses of events.antirez2013-01-281-4/+33
| | | | | | | | | When keyspace events are enabled, the overhead is not sever but noticeable, so this commit introduces the ability to select subclasses of events in order to avoid to generate events the user is not interested in. The events can be selected using redis.conf or CONFIG SET / GET.
* Keyspace events notification API.antirez2013-01-281-0/+17
|
* Fixed many typos.guiquanz2013-01-191-1/+1
|
* serverCron() frequency is now a runtime parameter (was REDIS_HZ).antirez2012-12-141-0/+17
| | | | | | | | | | | | | | | | | | | | | | | | | | | REDIS_HZ is the frequency our serverCron() function is called with. A more frequent call to this function results into less latency when the server is trying to handle very expansive background operations like mass expires of a lot of keys at the same time. Redis 2.4 used to have an HZ of 10. This was good enough with almost every setup, but the incremental key expiration algorithm was working a bit better under *extreme* pressure when HZ was set to 100 for Redis 2.6. However for most users a latency spike of 30 milliseconds when million of keys are expiring at the same time is acceptable, on the other hand a default HZ of 100 in Redis 2.6 was causing idle instances to use some CPU time compared to Redis 2.4. The CPU usage was in the order of 0.3% for an idle instance, however this is a shame as more energy is consumed by the server, if not important resources. This commit introduces HZ as a runtime parameter, that can be queried by INFO or CONFIG GET, and can be modified with CONFIG SET. At the same time the default frequency is set back to 10. In this way we default to a sane value of 10, but allows users to easily switch to values up to 500 for near real-time applications if needed and if they are willing to pay this small CPU usage penalty.
* Sentinel: added documentation about slave-priority in redis.confantirez2012-08-281-0/+15
|
* Limit memory used by big SLOWLOG entries.antirez2012-04-211-1/+1
| | | | | | | | | | | Two limits are added: 1) Up to SLOWLOG_ENTRY_MAX_ARGV arguments are logged. 2) Up to SLOWLOG_ENTRY_MAX_STRING bytes per argument are logged. 3) slowlog-max-len is set to 128 by default (was 1024). The number of remaining arguments / bytes is logged in the entry so that the user can understand better the nature of the logged command.
* redis.conf AOF section comments improved.antirez2012-04-201-16/+21
|
* It is now possible to enable/disable RDB checksum computation from ↵antirez2012-04-101-0/+9
| | | | redis.conf or via CONFIG SET/GET. Also CONFIG SET support added for rdbcompression as well.
* Comments about security of slave-read-only in redis.coinf.antirez2012-03-211-1/+9
|
View Lorry Controller Status