- 07 9月, 2014 1 次提交
-
-
由 jonathan pickett 提交于
-
- 15 8月, 2014 1 次提交
-
-
由 jonathan pickett 提交于
issue 161: Memory allocator not compiled to be thread safe. Background AOF fsync code (bio.c) was allocating memory. This caused heap corruption.
-
- 13 8月, 2014 1 次提交
-
-
由 jonathan pickett 提交于
-
- 01 8月, 2014 2 次提交
-
-
由 jonathan pickett 提交于
code review feedback on 432a38e53d7844a7bcf8131ddaa4c86d: moved heap memory mapped file into Redis sub directory under local app data folder
-
由 jonathan pickett 提交于
-
- 30 7月, 2014 1 次提交
-
-
由 jonathan pickett 提交于
-
- 29 7月, 2014 1 次提交
-
-
由 jonathan pickett 提交于
Service install with a full path to the conf file was failing. Part of this was due to not passing quotes along with arguments with spaces. The other part was not adding access allowed ACEs on all accessed paths.
-
- 24 7月, 2014 1 次提交
-
-
由 jonathan pickett 提交于
-
- 23 7月, 2014 2 次提交
-
-
由 jonathan pickett 提交于
-
由 jonathan pickett 提交于
-
- 22 7月, 2014 2 次提交
-
-
由 jonathan pickett 提交于
-
由 jonathan pickett 提交于
-
- 17 7月, 2014 1 次提交
-
-
由 jonathan pickett 提交于
Creation of QFork memory mapped file now respects the 'dir' .conf file directive. This allows for the QFork file to live in separate directory from the main executable.
-
- 16 7月, 2014 1 次提交
-
-
由 jonathan pickett 提交于
issue 145: there were a few places where our fwrite implementation was not used because of include file ordering
-
- 15 7月, 2014 1 次提交
-
-
由 jonathan pickett 提交于
-
- 08 7月, 2014 1 次提交
-
-
由 jonathan pickett 提交于
-
- 04 7月, 2014 2 次提交
-
-
由 jonathan pickett 提交于
-
由 jonathan pickett 提交于
issue 143: Added more detailed error messages for ERROR_COMMITMENT_LIMIT and ERROR_DISK_FULL errors in QFork code.
-
- 25 6月, 2014 1 次提交
-
-
由 jonathan pickett 提交于
-
- 24 6月, 2014 1 次提交
-
-
由 jonathan pickett 提交于
-
- 23 6月, 2014 6 次提交
-
-
由 antirez 提交于
-
由 antirez 提交于
-
由 antirez 提交于
-
由 Matt Stancliff 提交于
Some deployments need traffic sent from a specific address. This change uses the same policy as Cluster where the first listed bindaddr becomes the source address for outgoing Sentinel communication. Fixes #1667
-
由 Matt Stancliff 提交于
We need to access (bindaddr[0] || NULL) in a few places, so centralize access with a nice macro.
-
由 Matt Stancliff 提交于
Fixes #1826 (and many other reports of the same problem)
-
- 21 6月, 2014 14 次提交
-
-
由 antirez 提交于
-
由 antirez 提交于
-
由 antirez 提交于
This implements the new Sentinel-Client protocol for the Sentinel part: now instances are reconfigured using a transaction that ensures that the config is rewritten in the target instance, and that clients lose the connection with the instance, in order to be forced to: ask Sentinel, reconnect to the instance, and verify the instance role with the new ROLE command.
-
由 antirez 提交于
Added a new SKIPME option that is true by default, that prevents the client sending the command to be killed, unless SKIPME NO is sent.
-
由 antirez 提交于
-
由 antirez 提交于
-
由 antirez 提交于
This will be used by CLIENT KILL and is also a good way to ensure a given client is still the same across CLIENT LIST calls. The output of CLIENT LIST was modified to include the new ID, but this change is considered to be backward compatible as the API does not imply you can do positional parsing, since each filed as a different name.
-
由 antirez 提交于
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.
-
由 antirez 提交于
Info about the replication state with the master added.
-
由 antirez 提交于
The new ROLE command is designed in order to provide a client with informations about the replication in a fast and easy to use way compared to the INFO command where the same information is also available.
-
由 antirez 提交于
This commit adds peer ID caching in the client structure plus an API change and the use of sdsMakeRoomFor() in order to improve the reallocation pattern to generate the CLIENT LIST output. Both the changes account for a very significant speedup.
-
由 antirez 提交于
-
由 antirez 提交于
This commit also fixes a bug in the implementation of sdscatfmt() resulting from stale references to the SDS string header after sdsMakeRoomFor() calls.
-
由 antirez 提交于
sdscatprintf() relies on printf() family libc functions and is sometimes too slow in critical code paths. sdscatfmt() is an alternative which is: 1) Far less capable. 2) Format specifier uncompatible. 3) Faster. It is suitable to be used in those speed critical code paths such as CLIENT LIST output generation.
-