- 27 Aug, 2014 1 commit
-
-
Edgars Irmejs authored
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
-
- 28 Jul, 2014 1 commit
-
-
vps authored
-
- 25 Jul, 2014 1 commit
-
-
antirez authored
-
- 09 Jul, 2014 1 commit
-
-
antirez authored
This commit adds both support for redis.conf and CONFIG SET/GET.
-
- 21 Jun, 2014 1 commit
-
-
antirez authored
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.
-
- 22 Apr, 2014 1 commit
-
-
Kevin Menard authored
-
- 16 Apr, 2014 1 commit
-
-
antirez authored
-
- 31 Jan, 2014 3 commits
-
-
antirez authored
-
antirez authored
This is especially important since we already have a concept of backlog (the replication backlog).
-
Nenad Merdanovic authored
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.
-
- 19 Dec, 2013 3 commits
- 12 Dec, 2013 1 commit
-
-
Yubao Liu authored
-
- 06 Dec, 2013 1 commit
-
-
antirez authored
-
- 05 Dec, 2013 3 commits
-
-
Anurag Ramdasan authored
-
Anurag Ramdasan authored
-
antirez authored
-
- 11 Jul, 2013 2 commits
-
-
Geoff Garside authored
Add commented port6 and bind6 options to default redis.conf file.
- 08 Jul, 2013 1 commit
-
-
antirez authored
-
- 30 May, 2013 2 commits
- 27 May, 2013 1 commit
-
-
antirez authored
-
- 15 May, 2013 1 commit
-
-
antirez authored
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.
-
- 24 Apr, 2013 1 commit
-
-
antirez authored
-
- 06 Mar, 2013 1 commit
-
-
antirez authored
-
- 04 Mar, 2013 1 commit
-
-
Stam He authored
-
- 12 Feb, 2013 1 commit
-
-
antirez authored
-
- 11 Feb, 2013 2 commits
- 05 Feb, 2013 1 commit
-
-
antirez authored
-
- 04 Feb, 2013 1 commit
-
-
David Celis authored
Make several edits to the example redis.conf configuration file for improved flow and grammar. Signed-off-by:
David Celis <me@davidcel.is>
-
- 28 Jan, 2013 2 commits
-
-
antirez authored
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.
-
antirez authored
-
- 19 Jan, 2013 1 commit
-
-
guiquanz authored
Conflicts fixed, mainly because 2.8 has no cluster support / files: 00-RELEASENOTES src/cluster.c src/crc16.c src/redis-trib.rb src/redis.h
-
- 14 Dec, 2012 1 commit
-
-
antirez authored
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.
-
- 31 Aug, 2012 1 commit
-
-
antirez authored
-
- 21 Apr, 2012 2 commits
-
-
antirez authored
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.
-
antirez authored
-