- 26 6月, 2013 5 次提交
-
-
由 antirez 提交于
-
由 YAMAMOTO Takashi 提交于
time_t is always 64bit on recent versions of NetBSD.
-
由 YAMAMOTO Takashi 提交于
SUSv3 says that: The useconds argument shall be less than one million. If the value of useconds is 0, then the call has no effect. and actually NetBSD's implementation rejects such a value with EINVAL. use nanosleep which has no such a limitation instead.
-
由 YAMAMOTO Takashi 提交于
NetBSD-current's libc has a function named popcount. hiding these extensions using feature macros is not possible because redis uses other extensions covered by the same feature macro. eg. inet_aton
-
由 YAMAMOTO Takashi 提交于
on NetBSD, defining _XOPEN_SOURCE hides extensions like inet_aton, strcasecmp, etc.
-
- 20 6月, 2013 4 次提交
-
-
由 Jan-Erik Rediger 提交于
-
由 antirez 提交于
Sentinel 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
-
由 antirez 提交于
-
由 antirez 提交于
This fixes issue #1163
-
- 19 6月, 2013 5 次提交
-
-
由 antirez 提交于
When 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.
-
由 antirez 提交于
lua_pcall error handler now formats errors in a way more similar to luaPushError() so that errors generated in different contexts look alike.
-
由 antirez 提交于
When calling Lua scripts we try to report not just the error but information about the code line causing the error.
-
由 Marc-Antoine Perennou 提交于
Signed-off-by: NMarc-Antoine Perennou <Marc-Antoine@Perennou.com>
-
由 ioddly 提交于
-
- 04 6月, 2013 1 次提交
-
-
由 antirez 提交于
-
- 01 6月, 2013 1 次提交
-
-
由 antirez 提交于
-
- 31 5月, 2013 5 次提交
-
-
由 antirez 提交于
-
由 antirez 提交于
This way just after the CONFIG SET enabling the min-slaves feature it is possible to write to the database without delays.
-
由 antirez 提交于
When min-slaves-to-write feature is active, this field reports the number of slaves considered good (online state, lag within the specified range).
-
由 antirez 提交于
-
由 antirez 提交于
-
- 30 5月, 2013 6 次提交
-
-
由 antirez 提交于
-
由 antirez 提交于
I guess I needed another coffee...
-
由 antirez 提交于
This 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 提交于
-
由 antirez 提交于
-
由 antirez 提交于
There 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 5月, 2013 2 次提交
- 27 5月, 2013 8 次提交
-
-
由 antirez 提交于
-
由 antirez 提交于
-
由 antirez 提交于
Now 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 提交于
ACKs 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 提交于
Sending an ACK is now moved into the replicationSendAck() function.
-
由 antirez 提交于
-
由 antirez 提交于
-
由 antirez 提交于
This special command is used by the slave to inform the master the amount of replication stream it currently consumed. it does not return anything so that we not need to consume additional bandwidth needed by the master to reply something. The master can do a number of things knowing the amount of stream processed, such as understanding the "lag" in bytes of the slave, verify if a given command was already processed by the slave, and so forth.
-
- 25 5月, 2013 3 次提交
-
-
由 antirez 提交于
-
由 antirez 提交于
When master send commands, there is no need for the slave to reply. Redis used to queue the reply in the output buffer and discard the reply later, this is a waste of work and it is not clear why it was this way (I sincerely don't remember). This commit changes it in order to don't queue the reply at all. All tests passing.
-
由 antirez 提交于
We don't write the output buffer to the client socket for slaves only if the slave is not online.
-