summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* Use memtoll() when parsing the backlog-size option.config-rewriteantirez2013-05-151-1/+1
|
* CONFIG REWRITE: backlog size is a bytes option.antirez2013-05-151-1/+1
|
* CONFIG REWRITE: bindaddr -> bind.antirez2013-05-151-1/+1
|
* CONFIG REWRITE: when rewriting amount of bytes use GB, MB, KB if possible.antirez2013-05-151-7/+31
|
* CONFIG REWRITE: correctly escape the notify-keyspace-events option.antirez2013-05-151-1/+3
|
* CONFIG REWRITE: "active-rehashing" -> "activerehashing".antirez2013-05-151-1/+1
|
* CONFIG REWRITE: fixed typo in AOF fsync policy.antirez2013-05-151-1/+1
|
* CONFIG REWRITE: repl-disable-tcp-nodelay is a boolean option.antirez2013-05-151-1/+1
|
* Test default config modified to set logfile to empty string.antirez2013-05-151-1/+1
| | | | | Required because of recent changes in the way logfile is set to standard output.
* Added a define for most configuration defaults.antirez2013-05-154-55/+73
| | | | | | | | Also the logfile option was modified to always have an explicit value and to log to stdout when an empty string is used as log file. Previously there was special handling of the string "stdout" that set the logfile to NULL, this always required some special handling.
* CONFIG REWRITE: Use sane perms when creating redis.conf from scratch.antirez2013-05-141-1/+1
|
* CONFIG REWRITE: actually rewrite the config file, atomically.antirez2013-05-141-3/+63
|
* CONFIG REWRITE: remove orphaned lines.antirez2013-05-141-1/+43
|
* CONFIG REWRITE: strip multiple empty lines.antirez2013-05-141-1/+10
|
* CONFIG REWRITE: support for client-output-buffer-limit.antirez2013-05-133-11/+50
|
* CONFIG REWRITE: support for dir and slaveof.antirez2013-05-131-0/+12
|
* CONFIG REWRITE: support for save and syslog-facility.antirez2013-05-131-15/+40
|
* CONFIG REWRITE: Initial support code and design.antirez2013-05-133-4/+428
|
* Obtain absoute path of configuration file, expose it in INFO.antirez2013-05-092-2/+59
|
* Test: more PSYNC tests (backlog TTL).antirez2013-05-091-11/+37
|
* Version bumped to 2.9.10antirez2013-05-081-1/+1
|
* Test: check that replication partial sync works if we break the link.antirez2013-05-082-0/+80
| | | | | The test checks both successful syncs and unsuccessful ones by changing the backlog size.
* Test: various issues with the replication-4.tcl test fixed.antirez2013-05-081-7/+8
| | | | | The test actually worked, but vars for master and slave were inverted and sometimes used incorrectly.
* Revert "use long long instead of size_t make it more safe"antirez2013-05-082-3/+3
| | | | | | | | | | | | This reverts commit 2c75f2cf1aa0d9cc8256517bd6f3d8a82088ee1a. After further analysis, it is very unlikely that we'll raise the string size limit to > 512MB, and at the same time such big strings will be used in 32 bit systems. Better to revert to size_t so that 32 bit processors will not be forced to use a 64 bit counter in normal operations, that is currently completely useless.
* Merge pull request #1093 from july2993/unstableSalvatore Sanfilippo2013-05-082-3/+3
|\ | | | | in 32bit machine, popcount don't work with a input string length up to 5...
| * use long long instead of size_t make it more safeJiahao Huang2013-05-072-3/+3
| |
| * in 32bit machine, popcount don't work with a input string length up to 512 MB,Jiahao Huang2013-05-072-3/+3
| | | | | | | | bitcount commant may return negtive integer with string length more than 256 MB
* | Added more info about 32 bit builds into README.antirez2013-05-081-3/+14
|/
* Cluster: link reconnection on delayed PONG reply.antirez2013-05-032-3/+4
| | | | | | | | | | | | | | When the PONG delay is half the cluster node timeout, the link gets disconnected (and later automatically reconnected) in order to ensure that it's not just a dead connection issue. However this operation is only performed if the link is old enough, in order to avoid to disconnect the same link again and again (and among the other problems, never receive the PONG because of that). Note: when the link is reconnected, the 'ping_sent' field is not updated even if a new ping is sent using the new connection, so we can still reliably detect a node ping timeout.
* Cluster: restore PING sent time on reconnections.antirez2013-05-031-0/+8
|
* Cluster: PING/PONG handling redesigned.antirez2013-05-031-40/+61
|
* Cluster: process config from PING packets as we do for PONG.antirez2013-05-031-10/+15
| | | | | Also clusterBroadcastPing() was renamed into clusterBroadcastPong() that's what the function is actually doing.
* Cluster: createClusterLink() comment fixed for grammar.antirez2013-05-031-1/+1
|
* CONFIG SET server.masterauth aesthetic change.antirez2013-05-021-5/+1
| | | | | | This is just to make the code exactly like the above instance used for requirepass. No actual change nor the original code violated the Redis coding style.
* Reset masterauth if an empty string is configured.Michel Martens2013-05-021-1/+5
|
* Fix AOF bug: expire could be removed from key on AOF rewrite.charsyam2013-05-021-2/+3
| | | | | | | | | | | There was a race condition in the AOF rewrite code that, with bad enough timing, could cause a volatile key just about to expire to be turned into a non-volatile key. The bug was never reported to cause actualy issues, but was found analytically by an user in the Redis mailing list: https://groups.google.com/forum/?fromgroups=#!topic/redis-db/Kvh2FAGK4Uk This commit fixes issue #1079.
* Sentinel: changes to tilt mode.antirez2013-04-301-15/+26
| | | | | | | | | | | | | | | | | | | | | | Tilt mode was too aggressive (not processing INFO output), this resulted in a few problems: 1) Redirections were not followed when in tilt mode. This opened a window to misinform clients about the current master when a Sentinel was in tilt mode and a fail over happened during the time it was not able to update the state. 2) It was possible for a Sentinel exiting tilt mode to detect a false fail over start, if a slave rebooted with a wrong configuration about at the same time. This used to happen since in tilt mode we lose the information that the runid changed (reboot). Now instead the Sentinel in tilt mode will still remove the instance from the list of slaves if it changes state AND runid at the same time. Both are edge conditions but the changes should overall improve the reliability of Sentinel.
* Sentinel: more sensible delay in master demote after tilt.antirez2013-04-301-9/+11
|
* Lua updated to version 5.1.5.antirez2013-04-2922-136/+194
|
* Sentinel: only demote old master into slave under certain conditions.antirez2013-04-261-11/+46
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | We used to always turn a master into a slave if the DEMOTE flag was set, as this was a resurrecting master instance. However the following race condition is possible for a Sentinel that got partitioned or internal issues (tilt mode), and was not able to refresh the state in the meantime: 1) Sentinel X is running, master is instance "A". 3) "A" fails, sentinels will promote slave "B" as master. 2) Sentinel X goes down because of a network partition. 4) "A" returns available, Sentinels will demote it as a slave. 5) "B" fails, other Sentinels will promote slave "A" as master. 6) At this point Sentinel X comes back. When "X" comes back he thinks that: "B" is the master. "A" is the slave to demote. We want to avoid that Sentinel "X" will demote "A" into a slave. We also want that Sentinel "X" will detect that the conditions changed and will reconfigure itself to monitor the right master. There are two main ways for the Sentinel to reconfigure itself after this event: 1) If "B" is reachable and already configured as a slave by other sentinels, "X" will perform a redirection to "A". 2) If there are not the conditions to demote "A", the fact that "A" reports to be a master will trigger a failover detection in "X", that will end into a reconfiguraiton to monitor "A". However if the Sentinel was not reachable, its state may not be updated, so in case it titled, or was partiitoned from the master instance of the slave to demote, the new implementation waits some time (enough to guarantee we can detect the new INFO, and new DOWN conditions). If after some time still there are not the right condiitons to demote the instance, the DEMOTE flag is cleared.
* Sentinel: always redirect on master->slave transition.antirez2013-04-241-13/+9
| | | | | | | | | | | | | | | | | | Sentinel redirected to the master if the instance changed runid or it was the first time we got INFO, and a role change was detected from master to slave. While this is a good idea in case of slave->master, since otherwise we could detect a failover without good reasons just after a reboot with a slave with a wrong configuration, in the case of master->slave transition is much better to always perform the redirection for the following reasons: 1) A Sentinel may go down for some time. When it is back online there is no other way to understand there was a failover. 2) Pointing clients to a slave seems to be always the wrong thing to do. 3) There is no good rationale about handling things differently once an instance is rebooted (runid change) in that case.
* Config option to turn AOF rewrite incremental fsync on/off.antirez2013-04-245-1/+23
|
* AOF: sync data on disk every 32MB when rewriting.antirez2013-04-242-0/+2
| | | | | | | | | This prevents the kernel from putting too much stuff in the output buffers, doing too heavy I/O all at once. So the goal of this commit is to split the disk pressure due to the AOF rewrite process into smaller spikes. Please see issue #1019 for more information.
* rio.c: added ability to fdatasync() from time to time while writing.antirez2013-04-242-1/+33
|
* Test: fix RDB test checking file permissions.antirez2013-04-231-11/+24
| | | | | | | | | | | | When the test is executed using the root account, setting the permission to 222 does not work as expected, as root can read files with 222 permission. Now we skip the test if root is detected. This fixes issue #1034 and the duplicated #1040 issue. Thanks to Jan-Erik Rediger (@badboy on Github) for finding a way to reproduce the issue.
* Test: split conceptually unrelated comments in RDB test.antirez2013-04-221-1/+3
|
* Sentinel: turn old master into a slave when it comes back.antirez2013-04-191-2/+40
|
* More explicit panic message on out of memory.antirez2013-04-191-1/+1
|
* Cluster: fix clusterNode.name print format on debug message.xiaost72013-04-191-1/+1
| | | | | | It was %40s instead of %.40s, and since the string is not null terminated it caused random garbage to be displayed, and possibly a crash.
* Redis/Jemalloc Gitignore were too aggressive.antirez2013-04-182-7/+7
| | | | | | | | Redis gitignore was too aggressive since simply broken. Jemalloc gitignore was too agressive because it is conceived to just keep the files that allow to generate all the rest in development environments (so for instance the "configure" file is excluded).
View Lorry Controller Status