- 05 3月, 2014 1 次提交
-
-
由 antirez 提交于
-
- 13 2月, 2014 1 次提交
-
-
由 antirez 提交于
-
- 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.
-
- 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 1 次提交
-
-
由 antirez 提交于
-
- 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 17 次提交
-
-
由 antirez 提交于
-
由 antirez 提交于
-
由 antirez 提交于
-
由 antirez 提交于
-
由 antirez 提交于
-
由 antirez 提交于
-
由 antirez 提交于
-
由 antirez 提交于
-
由 antirez 提交于
-
由 antirez 提交于
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.
-
由 antirez 提交于
-
由 antirez 提交于
-
由 antirez 提交于
-
由 antirez 提交于
-
由 antirez 提交于
-
由 antirez 提交于
-
由 antirez 提交于
-