- 05 6月, 2014 2 次提交
-
-
由 antirez 提交于
-
由 antirez 提交于
The lua_to*string() family of functions use a non optimal format specifier when converting integers to strings. This has both the problem of the number being converted in exponential notation, which we don't use as a Redis return value when floating point numbers are involed, and, moreover, there is a loss of precision since the default format specifier is not able to represent numbers that must be represented exactly in the IEEE 754 number mantissa. The new code handles it as a special case using a saner conversion. This fixes issue #1118.
-
- 28 5月, 2014 1 次提交
-
-
由 antirez 提交于
-
- 27 5月, 2014 1 次提交
-
-
由 antirez 提交于
-
- 26 5月, 2014 5 次提交
-
-
由 Salvatore Sanfilippo 提交于
Fix test framework to detect proper server PID
-
由 Matt Stancliff 提交于
If we are in the signal handler, we don't want to handle the signal again. In extreme cases, this can cause a stack overflow and segfault Redis. Fixes #1771
-
由 antirez 提交于
There is a time defined by REDIS_CLUSTER_WRITABLE_DELAY where fail -> ok switch is not possible after startup as a master for some time, however the contrary (ok -> fail) should always be possible.
-
由 antirez 提交于
FLUSHALL will fail on read-only slaves, but there the command is not needed in order to reset the instance with CLUSTER RESET so errors can be ignored.
-
由 antirez 提交于
-
- 24 5月, 2014 1 次提交
-
-
由 Matt Stancliff 提交于
Previously the PID format was: [PID] Timestamp But it recently changed to: PID:X Timestamp The tcl testing framework was grabbing the PID from \[\d+\], but that's not valid anymore. Now we grab the pid from "PID: <PID>" in the part of Redis startup output to the right of the ASCII logo.
-
- 23 5月, 2014 5 次提交
-
-
由 antirez 提交于
-
由 antirez 提交于
-
由 antirez 提交于
Do things in a sequence that prevents failover during failure detection.
-
由 antirez 提交于
-
由 antirez 提交于
Every log contains, just after the pid, a single character that provides information about the role of an instance: S - Slave M - Master C - Writing child X - Sentinel
-
- 22 5月, 2014 4 次提交
-
-
由 antirez 提交于
Check the commit changes in the example redis.conf for more information.
-
由 antirez 提交于
The bug was triggered by running the test with Valgrind (which is a lot slower and more sensible to timing issues) after the recent changes that made Redis more promptly able to reply with the -LOADING error.
-
由 antirez 提交于
-
由 antirez 提交于
While iterating the list of nodes we want to set the slot as stable in the current node, not always in the first node of the list.
-
- 21 5月, 2014 2 次提交
- 20 5月, 2014 6 次提交
-
-
由 antirez 提交于
-
由 antirez 提交于
-
由 Salvatore Sanfilippo 提交于
Fix LUA_OBJCACHE segfault.
-
由 antirez 提交于
-
由 antirez 提交于
-
由 michael-grunder 提交于
When scanning the argument list inside of a redis.call() invocation for pre-cached values, there was no check being done that the argument we were on was in fact within the bounds of the cache size. So if a redis.call() command was ever executed with more than 32 arguments (current cache size #define setting) redis-server could segfault.
-
- 19 5月, 2014 5 次提交
-
-
由 antirez 提交于
-
由 Salvatore Sanfilippo 提交于
Correct the HyperLogLog stale cache flag to prevent unnecessary computat...
-
由 antirez 提交于
-
由 antirez 提交于
-
由 antirez 提交于
-
- 18 5月, 2014 1 次提交
-
-
由 Mike Trinkala 提交于
Set the MSB as documented.
-
- 15 5月, 2014 5 次提交
-
-
由 antirez 提交于
clusterHandleSlaveFailover() was reimplementing what clusterSetNodeAsMaster() without any good reason.
-
由 antirez 提交于
Thanks to this change, when there is some code like: clusterDoBeforeSleep(CLUSTER_TODO_UPDATE_STATE|...); ... and later before returning to the event loop ... clusterUpdateState(); The clusterUpdateState() function will clar the flag and will not be repeated in the clusterBeforeSleep() function. This especially important for config save/fsync flags which are slow to execute and not a good idea to repeat without a good reason. This is implemented for all the CLUSTER_TODO flags.
-
由 antirez 提交于
-
由 antirez 提交于
The new command is able to reset a cluster node so that it starts again as a fresh node. By default the command performs a soft reset (the same as calling it as CLUSTER RESET SOFT), and the following steps are performed: 1) All slots are set as unassigned. 2) The list of known nodes is flushed. 3) Node is set as master if it is a slave. When an hard reset is performed with CLUSTER RESET HARD the following additional operations are performed: 4) A new Node ID is created at random. 5) Epochs are set to 0. CLUSTER RESET is useful both when the sysadmin wants to reconfigure a node with a different role (for example turning a slave into a master) and for testing purposes. It also may play a role in automatically provisioned Redis Clusters, since it allows to reset a node back to the initial state in order to be reconfigured.
-
由 antirez 提交于
-
- 14 5月, 2014 2 次提交