summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* Cluster test: add tmp dir to Git repo.3.0.0-beta5antirez2014-05-261-0/+2
|
* Fix test framework to detect proper server PIDMatt Stancliff2014-05-261-1/+1
| | | | | | | | | | | | | | 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.
* Disable recursive watchdog signal handlerMatt Stancliff2014-05-261-1/+1
| | | | | | | | 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
* Redis 2.9.54 (Redis 3.0.0 beta-5).antirez2014-05-262-1/+7
|
* Cluster: always allow ok -> fail switch in clusterUpdateState().antirez2014-05-261-0/+1
| | | | | | 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.
* Cluster test: catch FLUSHALL errors on node reset.antirez2014-05-261-1/+1
| | | | | | 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.
* Sentinel example config: explain you don't need to specify slaves.antirez2014-05-261-0/+6
|
* Redis 2.9.53 (Redis 3.0.0 beta-4).3.0.0-beta4antirez2014-05-232-1/+41
|
* Cluster test: basic failover unit added.antirez2014-05-231-0/+35
|
* Cluster test: move basic read/write test into a procedure.antirez2014-05-232-9/+23
|
* Cluster test: more reliable 01-faildet unit.antirez2014-05-231-9/+15
| | | | Do things in a sequence that prevents failover during failure detection.
* 3.0 Changelog typo fixed. lost -> list.antirez2014-05-231-1/+1
|
* Document log format change in 3.0 Changelog.antirez2014-05-231-1/+7
|
* redisLogFromHandler() format changed to match new logs format.antirez2014-05-231-2/+1
|
* Tag every log line with role.antirez2014-05-232-1/+13
| | | | | | | | | | 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
* Cluster: slave validity factor is now user configurable.antirez2014-05-236-8/+69
| | | | Check the commit changes in the example redis.conf for more information.
* Test: AOF test false positive when running in slow hosts.antirez2014-05-231-1/+16
| | | | | | 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.
* Test: dump.tcl fixed for RESTORE new error msg.antirez2014-05-231-1/+1
|
* Fix an error in redis-trib where we always talk with same node.antirez2014-05-231-1/+3
| | | | | 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.
* redis-trib fix improved: move keys from N nodes to owner.antirez2014-05-231-15/+51
|
* redis-trib fix: use MIGRATE REPLACE when fixing slots.antirez2014-05-231-2/+13
| | | | This fixes issue #1765.
* Regression test for issue #1764.antirez2014-05-201-0/+13
|
* Remove trailing spaces from scripting.cantirez2014-05-201-3/+3
|
* Remove trailing spaces from sentinel.c.antirez2014-05-201-9/+9
|
* Fix LUA_OBJCACHE segfault.michael-grunder2014-05-201-1/+3
| | | | | | | | | | 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.
* Cluster test: better failure detection test and framework improvements.antirez2014-05-202-9/+43
|
* Cluster test: failure detection initial tests.antirez2014-05-202-0/+32
|
* Cluster test: proper initialization at unit startup.antirez2014-05-203-34/+41
|
* Cluster: use clusterSetNodeAsMaster() during slave failover.antirez2014-05-201-4/+1
| | | | | clusterHandleSlaveFailover() was reimplementing what clusterSetNodeAsMaster() without any good reason.
* Cluster: clear todo_before_sleep flags when executing actions.antirez2014-05-201-2/+12
| | | | | | | | | | | | | | | 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.
* Fixed typo in CLUSTER RESET implementation.antirez2014-05-201-1/+1
|
* CLUSTER RESET implemented.antirez2014-05-201-0/+88
| | | | | | | | | | | | | | | | | | | | | | | | | 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.
* Remove trailing spaces from cluster.c file.antirez2014-05-201-9/+9
|
* Cluster test: added function assert_cluster_state.antirez2014-05-202-10/+14
|
* Cluster: don't accept cluster bus connections during startup.antirez2014-05-201-0/+4
|
* Cluster: better handling of stolen slots.antirez2014-05-203-16/+47
| | | | | | | | | | | | | | | | | | The previous code handling a lost slot (by another master with an higher configuration for the slot) was defensive, considering it an error and putting the cluster in an odd state requiring redis-cli fix. This was changed, because actually this only happens either in a legitimate way, with failovers, or when the admin messed with the config in order to reconfigure the cluster. So the new code instead will try to make sure that the keys stored match the new slots map, by removing all the keys in the slots we lost ownership from. The function that deletes the keys from the lost slots is called only if the node does not lose all its slots (resulting in a reconfiguration as a slave of the node that got ownership). This is an optimization since the replication code will anyway flush all the instance data in a faster way.
* cluster.tcl: fix redis links leak in refresh_nodes_map.antirez2014-05-201-1/+7
|
* cluster.tcl: saner error handling.antirez2014-05-201-4/+18
| | | | | | | | | | Better handling of connection errors in order to update the table and recovery, populate the startup nodes table after fetching the list of nodes. More work to do about it, it is still not as reliable as redis-rb-cluster implementation which is the minimal reference implementation for Redis Cluster clients.
* redis.tcl: return I/O error message when peer closes connection.antirez2014-05-201-1/+4
|
* Cluster: fixed data_age computation / check integer overflow.antirez2014-05-201-3/+4
|
* Cluster: forced failover implemented.antirez2014-05-201-5/+27
| | | | | | | | | | | Using CLUSTER FAILOVER FORCE it is now possible to failover a master in a forced way, which means: 1) No check to understand if the master is up is performed. 2) No data age of the slave is checked. Evan a slave with very old data can manually failover a master in this way. 3) No chat with the master is attempted to reach its replication offset: the master can just be down.
* Cluster: bypass data_age check for manual failovers.antirez2014-05-201-4/+11
| | | | | | | | Automatic failovers only happen in Redis Cluster if the slave trying to be elected was disconnected from its master for no more than 10 times the node-timeout value. However there should be no such a check for manual failovers, since these are initiated by the sysadmin that, in theory, knows what she is doing when a slave is selected to be promoted.
* HyperLogLog regression test for issue #1762.antirez2014-05-191-0/+11
|
* Correct the HyperLogLog stale cache flag to prevent unnecessary computations.Mike Trinkala2014-05-191-4/+4
| | | | Set the MSB as documented.
* Fixed possible buffer overflow bug if RDB file is corrupted.Akos Vandra2014-05-121-1/+1
| | | | (Note: commit message modified by @antirez for clarity).
* fixed possible buffer overflow errorAkos Vandra2014-05-121-1/+1
|
* redis-trib create: use CONFIG SET-CONFIG-EPOCH before joining the cluster.antirez2014-05-121-0/+18
| | | | | | This way there is no need for the conflict resolution algo to be used in order to start with a cluster where each node has a different configEpoch.
* Sentinel: Add "dir /tmp" directive in example sentinel.conf.antirez2014-05-121-0/+7
|
* redis-trib import: trap MIGRATE errors.antirez2014-05-121-2/+9
|
* redis-trib.rb: MIGRATE hardcoded timeout set to 15 sec.antirez2014-05-121-2/+2
| | | | | | Will be configurable / adaptive at some point but let's start with a saner value compared to 1 sec which is not a good idea for big data structures stored into a single key.
View Lorry Controller Status