- 18 Mar, 2015 8 commits
-
-
antirez authored
Related to issue #2372.
-
Mariano Pérez Rodríguez authored
Fixing #2371 as per @mattsta's suggestion
-
antirez authored
Backtrace is a glibc extension, while setproctitle() implementation depends on the memory layout and is partially libc dependent.
-
antirez authored
-
antirez authored
Less grays: more readable palette since usually we have a non linear distribution of percentages and very near gray tones are hard to take apart. Final part of the palette is gradient from yellow to red. The red part is hardly reached because of usual distribution of latencies, but shows up mainly when latencies are very high because of the logarithmic scale, this is coherent to what people expect: red = bad.
-
Masahiko Sawada authored
-
Michel Martens authored
-
antirez authored
-
- 13 Mar, 2015 1 commit
-
-
Leandro López (inkel) authored
When trying to debug sentinel connections or max connections errors it would be very useful to have the ability to see the list of connected clients to a running sentinel. At the same time it would be very helpful to be able to name each sentinel connection or kill offending clients. This commits adds the already defined CLIENT commands back to Redis Sentinel.
-
- 08 Mar, 2015 1 commit
-
-
antirez authored
-
- 04 Mar, 2015 1 commit
-
-
antirez authored
Itereator misuse due to analyzeLatencyForEvent() accessing the dictionary during the iteration, without the iterator being reclared as safe.
-
- 27 Feb, 2015 1 commit
-
-
antirez authored
-
- 26 Feb, 2015 2 commits
-
-
antirez authored
1. Remove useless "cs" initialization. 2. Add a "select" var to capture a condition checked multiple times. 3. Avoid duplication of the same if (!copy) conditional. 4. Don't increment dirty if copy is given (no deletion is performed), otherwise we propagate MIGRATE when not needed.
-
Salvatore Sanfilippo authored
Add last_dbid to migrateCachedSocket to avoid redundant SELECT
-
- 25 Feb, 2015 1 commit
-
-
Tommy Wang authored
Avoid redundant SELECT calls when continuously migrating keys to the same dbid within a target Redis instance.
-
- 13 Feb, 2015 2 commits
- 12 Feb, 2015 4 commits
-
-
antirez authored
-
antirez authored
Related to PR #2357.
-
antirez authored
Related to PR #2357.
-
Chris Lamb authored
Signed-off-by:
Chris Lamb <chris@chris-lamb.co.uk>
-
- 11 Feb, 2015 14 commits
-
-
antirez authored
-
antirez authored
-
antirez authored
Fixed by @oranagra, thank you.
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
Avoid code repetition introduced with PR #2367, also fixes the return value to always return 0 if there is nothing more to rehash.
-
Sun He authored
-
antirez authored
This is very similar to the optimization applied to dictGetRandomKeys, but applied to the single key variant. Related to issue #2306.
-
antirez authored
Related to issue #2306.
-
antirez authored
We use the invariant that the original table ht[0] is never populated up to the index before the current rehashing index. Related to issue #2306.
-
antirez authored
Related to issue #2306.
-
antirez authored
Related to issue #2306.
-
antirez authored
Related to issue #2306.
-
- 10 Feb, 2015 5 commits
-
-
antirez authored
-
Charles Hooper authored
-
antirez authored
-
antirez authored
--stat mode already used to reconnect automatically if the server is no longer available. This is useful since this is an interactive mode used for debugging, however the same applies to --latency and --latency-dist modes, so now both use the reconnecting command execution as well. The reconnection code was modified to use basic VT100 escape sequences in order to play better with different kinds of output on the screen when the reconnection happens, and to hide the reconnection attempt output when finally the reconnection happens.
-
antirez authored
So far not able to find a color palette within the 256 colors which is not confusing. However I believe it is a possible task, so will try better later.
-