- 24 Jun, 2013 3 commits
- 
- 
antirez authoredIt should be called just one time at startup and not every time the Lua scripting engine is re-initialized, otherwise memory is leaked. 
- 
antirez authoredThis commit uses the Replication Script Cache in order to avoid translating EVALSHA into EVAL whenever possible for both the AOF and slaves. 
- 
antirez authoredThis code is only responsible to take an LRU-evicted fixed length cache of SHA1 that we are sure all the slaves received. In this commit only the implementation is provided, but the Redis core does not use it to actually send EVALSHA to slaves when possible. 
 
- 
- 21 Jun, 2013 1 commit
- 
- 
antirez authoredThe old REDIS_CMD_FORCE_REPLICATION flag was removed from the implementation of Redis, now there is a new API to force specific executions of a command to be propagated to AOF / Replication link: void forceCommandPropagation(int flags); The new API is also compatible with Lua scripting, so a script that will execute commands that are forced to be propagated, will also be propagated itself accordingly even if no change to data is operated. As a side effect, this new design fixes the issue with scripts not able to propagate PUBLISH to slaves (issue #873).
 
- 
- 20 Jun, 2013 5 commits
- 
- 
Salvatore Sanfilippo authoredInitialize char* to NULL to remove compiler warning 
- 
Jan-Erik Rediger authored
- 
antirez authoredThe result is an empty list but it is handy to call it programmatically. 
- 
antirez authoredCurrently it implements three subcommands: PUBSUB CHANNELS [<pattern>] List channels with non-zero subscribers. PUBSUB NUMSUB [channel_1 ...] List number of subscribers for channels. PUBSUB NUMPAT Return number of subscribed patterns. 
- 
antirez authoredSentinel was not able to detect slaves when connected to a very recent version of Redis master since a previos non-backward compatible change to INFO broken the parsing of the slaves ip:port INFO output. This fixes issue #1164 
 
- 
- 19 Jun, 2013 4 commits
- 
- 
antirez authored
- 
antirez authored
- 
antirez authoredThis fixes issue #1163 
- 
antirez authoredWhen the semantics changed from logfile = NULL to logfile = "" to log into standard output, no proper change was made to logStackTrace() to make it able to work with the new setup. This commit fixes the issue. 
 
- 
- 18 Jun, 2013 2 commits
- 17 Jun, 2013 2 commits
- 
- 
Salvatore Sanfilippo authoredTry to report source of bad Lua API calls 
- 
Salvatore Sanfilippo authoredtest-server: only listen to 127.0.0.1 
 
- 
- 12 Jun, 2013 2 commits
- 
- 
Marc-Antoine Perennou authoredSigned-off-by:Marc-Antoine Perennou <Marc-Antoine@Perennou.com> 
- 
antirez authored
 
- 
- 11 Jun, 2013 1 commit
- 
- 
antirez authored
 
- 
- 04 Jun, 2013 1 commit
- 
- 
antirez authored
 
- 
- 31 May, 2013 2 commits
- 30 May, 2013 8 commits
- 
- 
antirez authored
- 
antirez authoredThis way just after the CONFIG SET enabling the min-slaves feature it is possible to write to the database without delays. 
- 
antirez authoredWhen min-slaves-to-write feature is active, this field reports the number of slaves considered good (online state, lag within the specified range). 
- 
antirez authored
- 
antirez authored
- 
antirez authoredI guess I needed another coffee... 
- 
antirez authoredThis feature allows the user to specify the minimum number of connected replicas having a lag less or equal than the specified amount of seconds for writes to be accepted. 
- 
antirez authored
 
- 
- 29 May, 2013 2 commits
- 
- 
antirez authored
- 
antirez authoredThere is a new 'lag' information in the list of slaves, in the "replication" section of the INFO output. Also the format was changed in a backward incompatible way in order to make it more easy to parse if new fields are added in the future, as the new format is comma separated but has named fields (no longer positional fields). 
 
- 
- 28 May, 2013 1 commit
- 
- 
antirez authored
 
- 
- 27 May, 2013 6 commits
- 
- 
antirez authored
- 
antirez authored
- 
antirez authored
- 
antirez authoredNow masters, using the time at which the last REPLCONF ACK was received, are able to explicitly disconnect slaves that are no longer responding. Previously the only chance was to see a very long output buffer, that was highly suboptimal. 
- 
antirez authoredACKs can be also used as a base for synchronous replication. However in that case they'll be explicitly requested by the master when the client sends a request that needs to be replicated synchronously. 
- 
antirez authoredSending an ACK is now moved into the replicationSendAck() function. 
 
-