- 13 1月, 2015 2 次提交
-
-
由 antirez 提交于
Also explicitly set version to 0, add a protocol version define, improve comments in the gossip structure. Note that the structure layout is the same after the change, we are just making the padding explicit with an additional not used 16 bits field. So this commit is still able to talk with the previous versions of cluster nodes.
-
由 antirez 提交于
Valgrind checks that the buffers we transfer via syscalls are all composed of bytes actually initialized. This is useful, it makes we able to avoid leaking informations in non initialized parts fo messages transferred to other hosts. This commit fixes one of such issues.
-
- 12 1月, 2015 1 次提交
-
-
由 antirez 提交于
Can't be initialized by resetManualFailover() since it's actual state the function uses, so we need to initialize it at startup time. Not really a bug in practical terms, but showed up into valgrind and is not technically correct anyway.
-
- 09 1月, 2015 7 次提交
-
-
由 antirez 提交于
This fix is from @NanXiao, however I was not able to retain authorship because the Pull Request original repository was removed.
-
由 antirez 提交于
-
由 antirez 提交于
-
由 antirez 提交于
Before this commit scripts were able to access / create keys outside the set of hash slots served by the local node.
-
由 Matt Stancliff 提交于
-
由 Matt Stancliff 提交于
Under certain conditions the node list wasn't being fully populated and 'create' would fail trying to call methods on nil objects.
-
由 Matt Stancliff 提交于
This tiny bit of code has gone through so many revisions. Hopefully it's more correct now. Fixes #2204
-
- 08 1月, 2015 3 次提交
-
-
由 antirez 提交于
-
由 Jungtaek Lim 提交于
-
由 antirez 提交于
-
- 23 12月, 2014 1 次提交
-
-
由 antirez 提交于
1. Server unxtime may remain not updated while loading AOF, so ETA is not updated correctly. 2. Number of processed byte was not initialized. 3. Possible division by zero condition (likely cause of issue #1932).
-
- 22 12月, 2014 1 次提交
-
-
由 Alon Diamant 提交于
-
- 19 12月, 2014 1 次提交
-
-
由 antirez 提交于
Fixes issue #2225.
-
- 18 12月, 2014 1 次提交
-
-
由 Matt Stancliff 提交于
If we woke up to accept a connection, but we can't accept it, inform the user of the error going on with their networking. (The previous message was the same for success or error!)
-
- 17 12月, 2014 1 次提交
-
-
由 Rhommel Lamas 提交于
-
- 16 12月, 2014 1 次提交
-
-
由 antirez 提交于
-
- 15 12月, 2014 1 次提交
-
-
由 antirez 提交于
-
- 13 12月, 2014 4 次提交
-
-
由 antirez 提交于
Otherwise there are security risks, especially when providing Redis as a service, the user may "sniff" for admin commands renamed to an unguessable string via rename-command in redis.conf.
-
由 antirez 提交于
The old list did not made much sense... and the flag is currently not used at all, so no side effects.
-
由 Rhommel Lamas 提交于
-
由 antirez 提交于
It fixes a bad bug that crashes the server in certain conditions as shown in issue #2210.
-
- 11 12月, 2014 8 次提交
-
-
由 antirez 提交于
Related to #2094.
-
由 Matt Stancliff 提交于
People mostly use SORT against lists, but our prior behavior was pretending lists were an unordered bag requiring a forced-sort when no sort was requested. We can just use the native list ordering to ensure consistency across replicaion and scripting calls. Closes #2079 Closes #545 (again)
-
由 zhanghailei 提交于
-
由 Ben Dowling 提交于
status command currently reports success when redis has crashed and the pid file still exists. Changing to check the actual process is running.
-
由 一个手艺人 提交于
Fix function prototype in redis-cli.c.
-
由 Matt Stancliff 提交于
-
由 h0x91b 提交于
if redis works in cluster-mode and redis-cli was run with argv, reconnect if needs. example: ./redis-cli set foo bar if return is MOVED redis-cli just do nothing.
-
由 Mariano Pérez Rodríguez 提交于
Fix two typos in redis.conf: - "trnasfers" --> "transfers" - "enalbed" --> "enabled"
-
- 09 12月, 2014 8 次提交
-
-
由 Sun He 提交于
-
由 Deepak Verma 提交于
-
由 azure provisioned user 提交于
-
由 Sun He 提交于
-
由 Sun He 提交于
-
由 Sun He 提交于
-
由 antirez 提交于
10000 completes in a too short time and may easily provide unreliable figures because of tiny duration.
-
由 Matthias Petschick 提交于
-