- 12 6月, 2014 1 次提交
-
-
由 jonathan pickett 提交于
issue 123: changed error output in Win32_service and Win32_QFork to use redisLog. Also fixed a few compiler warnings.
-
- 17 4月, 2014 1 次提交
-
-
由 jonathan pickett 提交于
fdapi not properly mapping fstat in config.c, so we ended up invoking CRT version without the rfd->fd translation resulting in the CRT calling exit(). Fixes issue 43.
-
- 16 4月, 2014 1 次提交
-
-
由 antirez 提交于
-
- 25 3月, 2014 1 次提交
-
-
由 Matt Stancliff 提交于
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.
-
- 21 3月, 2014 1 次提交
-
-
由 antirez 提交于
Now CONFIG RESETSTAT makes sure to reset all the fields, and in the future it will be simpler to avoid missing new fields.
-
- 11 3月, 2014 1 次提交
-
-
由 Matt Stancliff 提交于
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
-
- 08 3月, 2014 1 次提交
-
-
由 jonathan pickett 提交于
Added --maxheap flag to control size of memory mapped file created. Heap can now exceed size of physical memory. See long comment in Win32_qfork.cpp about implications of using --maxheap flag.
-
- 05 3月, 2014 2 次提交
- 26 2月, 2014 1 次提交
-
-
由 jonathan pickett 提交于
-
- 18 2月, 2014 1 次提交
-
-
由 jonathan pickett 提交于
Removing maxheapgb flag in favor of utilizing existing maxmemory flag. Now honoring maxmemory flag in .conf files. Slightly modified default MMF startup requirements to [phys - min(0.2*phys, 3GB)]
-
- 13 2月, 2014 1 次提交
-
-
由 antirez 提交于
-
- 06 2月, 2014 1 次提交
-
-
由 Jonathan Pickett 提交于
-
- 31 1月, 2014 2 次提交
-
-
由 antirez 提交于
This is especially important since we already have a concept of backlog (the replication backlog).
-
由 Nenad Merdanovic 提交于
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.
-
- 28 1月, 2014 1 次提交
-
-
由 Jonathan Pickett 提交于
-
- 23 12月, 2013 1 次提交
-
-
由 antirez 提交于
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.
-
- 19 12月, 2013 4 次提交
-
-
由 antirez 提交于
CONFIG REWRITE is now wiser and does not touch what it does not understand inside redis.conf.
-
由 Yubao Liu 提交于
Those options will be thrown without this patch: include, rename-command, min-slaves-to-write, min-slaves-max-lag, appendfilename.
-
由 antirez 提交于
-
由 antirez 提交于
With this commit options not explicitly rewritten by CONFIG REWRITE are not touched at all. These include new options that may not have support for REWRITE, and other special cases like rename-command and include.
-
- 21 11月, 2013 3 次提交
-
-
由 antirez 提交于
At the end of the file, CONFIG REWRITE adds a comment line that: # Generated by CONFIG REWRITE Followed by the additional config options required. However this was added again and again at every rewrite in praticular conditions (when a given set of options change in a given time during the time). Now if it was alrady encountered, it is not added a second time. This is especially important for Sentinel that rewrites the config at every state change.
-
由 antirez 提交于
-
由 antirez 提交于
-
- 04 10月, 2013 2 次提交
-
-
由 antirez 提交于
-
由 Jonathan Pickett 提交于
Fix for issue #59. Generated FDs are used everywhere until a SOCKET handle is used by the Winsock APIs. The win32_socketmap code generates the simulated FDs and handles the mapping from these to socket handles.
-
- 22 7月, 2013 1 次提交
-
-
由 Henry Rawas 提交于
-
- 18 7月, 2013 1 次提交
-
-
由 antirez 提交于
-
- 08 7月, 2013 1 次提交
-
-
由 antirez 提交于
-
- 02 7月, 2013 1 次提交
-
-
由 antirez 提交于
This fixes issue #1094.
-
- 01 7月, 2013 1 次提交
-
-
由 antirez 提交于
-
- 26 6月, 2013 1 次提交
-
-
由 YAMAMOTO Takashi 提交于
time_t is always 64bit on recent versions of NetBSD.
-
- 20 6月, 2013 1 次提交
-
-
由 Jan-Erik Rediger 提交于
-
- 01 6月, 2013 1 次提交
-
-
由 antirez 提交于
-
- 31 5月, 2013 1 次提交
-
-
由 antirez 提交于
This way just after the CONFIG SET enabling the min-slaves feature it is possible to write to the database without delays.
-
- 30 5月, 2013 1 次提交
-
-
由 antirez 提交于
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.
-
- 18 5月, 2013 1 次提交
-
-
由 antirez 提交于
Should be "continue" and was "return". This fixes issue #1110
-
- 15 5月, 2013 3 次提交