- 11 7月, 2013 6 次提交
-
-
由 antirez 提交于
-
由 antirez 提交于
-
由 antirez 提交于
-
由 Geoff Garside 提交于
-
由 Geoff Garside 提交于
-
由 Geoff Garside 提交于
-
- 08 7月, 2013 3 次提交
- 02 7月, 2013 1 次提交
-
-
由 antirez 提交于
-
- 01 7月, 2013 1 次提交
-
-
由 antirez 提交于
-
- 27 6月, 2013 1 次提交
-
-
由 antirez 提交于
-
- 26 6月, 2013 6 次提交
-
-
由 antirez 提交于
It should be called just one time at startup and not every time the Lua scripting engine is re-initialized, otherwise memory is leaked.
-
由 antirez 提交于
This commit uses the Replication Script Cache in order to avoid translating EVALSHA into EVAL whenever possible for both the AOF and slaves.
-
由 antirez 提交于
This code is only responsible to take an LRU-evicted fixed length cache of SHA1 that we are sure all the slaves received. In this commit only the implementation is provided, but the Redis core does not use it to actually send EVALSHA to slaves when possible.
-
由 antirez 提交于
The old REDIS_CMD_FORCE_REPLICATION flag was removed from the implementation of Redis, now there is a new API to force specific executions of a command to be propagated to AOF / Replication link: void forceCommandPropagation(int flags); The new API is also compatible with Lua scripting, so a script that will execute commands that are forced to be propagated, will also be propagated itself accordingly even if no change to data is operated. As a side effect, this new design fixes the issue with scripts not able to propagate PUBLISH to slaves (issue #873).
-
由 antirez 提交于
Currently it implements three subcommands: PUBSUB CHANNELS [<pattern>] List channels with non-zero subscribers. PUBSUB NUMSUB [channel_1 ...] List number of subscribers for channels. PUBSUB NUMPAT Return number of subscribed patterns.
-
由 YAMAMOTO Takashi 提交于
time_t is always 64bit on recent versions of NetBSD.
-
- 31 5月, 2013 1 次提交
-
-
由 antirez 提交于
When min-slaves-to-write feature is active, this field reports the number of slaves considered good (online state, lag within the specified range).
-
- 30 5月, 2013 4 次提交
-
-
由 antirez 提交于
I guess I needed another coffee...
-
由 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.
-
由 antirez 提交于
-
由 antirez 提交于
There is a new 'lag' information in the list of slaves, in the "replication" section of the INFO output. Also the format was changed in a backward incompatible way in order to make it more easy to parse if new fields are added in the future, as the new format is comma separated but has named fields (no longer positional fields).
-
- 28 5月, 2013 1 次提交
-
-
由 antirez 提交于
-
- 27 5月, 2013 2 次提交
- 15 5月, 2013 4 次提交
-
-
由 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 提交于
-
- 24 4月, 2013 1 次提交
-
-
由 antirez 提交于
-
- 19 4月, 2013 1 次提交
-
-
由 antirez 提交于
-
- 02 4月, 2013 1 次提交
-
-
由 antirez 提交于
When a BGSAVE fails, Redis used to flood itself trying to BGSAVE at every next cron call, that is either 10 or 100 times per second depending on configuration and server version. This commit does not allow a new automatic BGSAVE attempt to be performed before a few seconds delay (currently 5). This avoids both the auto-flood problem and filling the disk with logs at a serious rate. The five seconds limit, considering a log entry of 200 bytes, will use less than 4 MB of disk space per day that is reasonable, the sysadmin should notice before of catastrofic events especially since by default Redis will stop serving write queries after the first failed BGSAVE. This fixes issue #849
-
- 28 3月, 2013 2 次提交
- 26 3月, 2013 2 次提交
- 13 3月, 2013 3 次提交
-
-
由 antirez 提交于
server.repl_down_since used to be initialized to the current time at startup. This is wrong since the replication never started. Clients testing this filed to check if data is uptodate should never believe data is recent if we never ever connected to our master.
-
由 Damian Janowski 提交于
This fixes cases where the RDB file does exist but can't be accessed for any reason. For instance, when the Redis process doesn't have enough permissions on the file.
-
由 antirez 提交于
It was placed for error in initServer() that's called after the configuation is already loaded, causing issue #1000.
-