- 21 Jul, 2015 1 commit
-
-
Oran Agra authored
-
- 16 Jul, 2015 1 commit
-
-
Jiahao Huang authored
-
- 12 Mar, 2015 2 commits
- 11 Mar, 2015 3 commits
- 10 Mar, 2015 2 commits
-
-
antirez authored
-
antirez authored
Not perfect since The Solution IMHO is to have a DSL with a table of configuration functions with type, limits, and aux functions to handle the odd ones. However this hacky macro solution is already better and forces to put limits in the range of numerical fields. More field types to be refactored in the next commits hopefully.
-
- 08 Mar, 2015 1 commit
-
-
antirez authored
-
- 12 Feb, 2015 1 commit
-
-
antirez authored
Related to PR #2357.
-
- 04 Feb, 2015 1 commit
-
-
Chris Lamb authored
Signed-off-by:
Chris Lamb <chris@chris-lamb.co.uk>
-
- 09 Jan, 2015 1 commit
-
-
Matt Stancliff authored
Adds configuration option 'supervised [no | upstart | systemd | auto]' Also removed 'bzero' from the previous implementation because it's 2015. (We could actually statically initialize those structs, but clang throws an invalid warning when we try, so it looks bad even though it isn't bad.) Fixes #2264
-
- 02 Jan, 2015 1 commit
-
-
Matt Stancliff authored
This removes: - list-max-ziplist-entries - list-max-ziplist-value This adds: - list-max-ziplist-size - list-compress-depth Also updates config file with new sections and updates tests to use quicklist settings instead of old list settings.
-
- 11 Dec, 2014 1 commit
-
-
Matt Stancliff authored
Also refactors getting human string values from the defined value in `server.maxmemory_policy` into a common function.
-
- 27 Oct, 2014 1 commit
-
-
antirez authored
-
- 16 Oct, 2014 1 commit
-
-
antirez authored
-
- 29 Sep, 2014 1 commit
-
-
Ezequiel Lovelle authored
Closes #2029
-
- 17 Sep, 2014 1 commit
-
-
antirez authored
-
- 08 Sep, 2014 1 commit
-
-
antirez authored
-
- 04 Sep, 2014 1 commit
-
-
antirez authored
The original implementation was modified in order to allow to selectively announce a different IP or port, and to rewrite the two options in the config file after a rewrite.
-
- 13 Aug, 2014 1 commit
-
-
antirez authored
-
- 08 Aug, 2014 1 commit
-
-
cubicdaiya authored
According to the C standard, it is desirable to give the type 'void' to functions have no argument. Closes #1631
-
- 02 Jul, 2014 1 commit
-
-
antirez authored
This commit adds both support for redis.conf and CONFIG SET/GET.
-
- 26 Jun, 2014 1 commit
-
-
antirez authored
-
- 16 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 May, 2014 1 commit
-
-
antirez authored
Check the commit changes in the example redis.conf for more information.
-
- 15 Apr, 2014 1 commit
-
-
antirez authored
-
- 24 Mar, 2014 1 commit
-
-
Matt Stancliff authored
Everywhere in the Redis code base, maxclients is treated as an int with (int)maxclients or `maxclients = atoi(source)`, so let's make maxclients an int. This fixes a bug where someone could specify a negative maxclients on startup and it would work (as well as set maxclients very high) because: unsigned int maxclients; char *update = "-300"; maxclients = atoi(update); if (maxclients < 1) goto fail; But, (maxclients < 1) can only catch the case when maxclients is exactly 0. maxclients happily sets itself to -300, which isn't -300, but rather 4294966996, which isn't < 1, so... everything "worked." maxclients config parsing checks for the case of < 1, but maxclients CONFIG SET parsing was checking for case of < 0 (allowing maxclients to be set to 0). CONFIG SET parsing is now updated to match config parsing of < 1. It's tempting to add a MINIMUM_CLIENTS define, but... I didn't. These changes were inspired by antirez#356, but this doesn't fix that issue.
-
- 19 Mar, 2014 1 commit
-
-
antirez authored
Now CONFIG RESETSTAT makes sure to reset all the fields, and in the future it will be simpler to avoid missing new fields.
-
- 06 Mar, 2014 1 commit
-
-
Matt Stancliff authored
This value needs to be set to zero (in addition to stat_numcommands) or else people may see a negative operations per second count after they run CONFIG RESETSTAT. Fixes antirez/redis#1577
-
- 05 Mar, 2014 1 commit
-
-
antirez authored
-
- 04 Mar, 2014 1 commit
-
-
antirez authored
-
- 13 Feb, 2014 1 commit
-
-
antirez authored
-
- 31 Jan, 2014 3 commits
-
-
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.
-
antirez authored
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.
-
- 20 Jan, 2014 2 commits
- 23 Dec, 2013 1 commit
-
-
antirez authored
There were two problems with the implementation. 1) "save" was not correctly processed when no save point was configured, as reported in issue #1416. 2) The way the code checked if an option existed in the "processed" dictionary was wrong, as we add the element with as a key associated with a NULL value, so dictFetchValue() can't be used to check for existance, but dictFind() must be used, that returns NULL only if the entry does not exist at all.
-