- 06 3月, 2013 10 次提交
-
-
由 antirez 提交于
-
由 antirez 提交于
Usually this does not happens since we trim for " \t\r\n", but if there are other chars that return true with isspace(), we may end with an empty argv. Better to handle the condition in an explicit way.
-
由 antirez 提交于
-
由 antirez 提交于
-
由 antirez 提交于
-
由 antirez 提交于
-
由 antirez 提交于
This makes programs not checking the return value for NULL much safer since with this change: 1) It is still possible to iterate the zero-length result without crashes. 2) sdssplitargs_free will work against NULL and 0 count.
-
由 antirez 提交于
An empty input string also resulted into the function returning NULL making it harder for the caller to distinguish between error and empty string without checking the original input string length.
-
由 charsyam 提交于
-
由 antirez 提交于
While Redis is loading the AOF or RDB file in memory only a subset of commands are allowed. This commit adds AUTH to this subset.
-
- 05 3月, 2013 11 次提交
-
-
由 antirez 提交于
-
由 antirez 提交于
If we have a master in FAIL state that's reachable again, and apparently no one is going to serve its slots, clear the FAIL flag and let the cluster continue with its operations again.
-
由 antirez 提交于
This is the unix time at which we set the FAIL flag for the node. It is only valid if FAIL is set. The idea is to use it in order to make the cluster more robust, for instance in order to revert a FAIL state if it is long-standing but still slots are assigned to this node, that is, no one is going to fix these slots apparently.
-
由 antirez 提交于
Usually we redirect clients to the right hash slot, however we don't want to do that with our master, we want just to mirror it.
-
由 antirez 提交于
-
由 antirez 提交于
-
由 antirez 提交于
-
由 antirez 提交于
Usually we try to send just 1 ping every second, however when we detect we are going to have unreliable failure detection because we can't ping some node in time, send an additional ping. This should only happen with very large clusters or when the the node timeout is set to a very low value.
-
由 antirez 提交于
-
由 antirez 提交于
If we are a cluster node the DB content will not match our configured slots. Don't do the check at all.
-
由 antirez 提交于
There are pathological cases where the line can be even longer a single node may contain all the slots in importing/migrating state.
-
- 04 3月, 2013 8 次提交
-
-
由 antirez 提交于
-
由 antirez 提交于
-
由 antirez 提交于
We now have replicationSetMaster() and replicationUnsetMaster() that can be called in other contexts (for instance Redis Cluster).
-
由 antirez 提交于
-
由 charsyam 提交于
adding check error code
-
由 antirez 提交于
This should improve things in two ways: 1) Prevent timeouts caused by the execution of long commands. 2) Improve detection of real connection errors. This is mostly effective only on Linux because of the bogus default keepalive settings. In Linux we have OS-specific calls to set the keepalive interval to reasonable values.
-
由 Salvatore Sanfilippo 提交于
suppress external diff program when using git diff.
-
由 stamhe 提交于
-
- 28 2月, 2013 11 次提交
-
-
由 antirez 提交于
As stated in the comment this is usually due to a resharding in progress so the client should be still redirected to the old node that will handle the redirection elsewhere.
-
由 antirez 提交于
The new code makes sure that the node slots bitmap is always consistent with the cluster->slots array.
-
由 antirez 提交于
-
由 antirez 提交于
-
由 antirez 提交于
Before a relatively slow popcount() operation was needed every time we needed to get the number of slots served by a given cluster node. Now we just need to check an integer that is taken in sync with the bitmap.
-
由 antirez 提交于
-
由 antirez 提交于
-
由 antirez 提交于
-
由 antirez 提交于
-
由 antirez 提交于
-
由 antirez 提交于
-