- 25 2月, 2013 10 次提交
-
-
由 antirez 提交于
Not sure why I set a limit to 1 million keys, there is no reason for this artificial limit, and anyway this is s a stupid limit because it is already high enough to create latency issues. So let's the users shoot on their feet because maybe they just actually know what they are doing.
-
由 antirez 提交于
-
由 antirez 提交于
-
由 antirez 提交于
The new sub-command uses the new countKeysInSlot() API and allows a cluster client to get the number of keys for a given hashslot.
-
由 antirez 提交于
-
由 antirez 提交于
-
由 antirez 提交于
Redis functions start in low case. A few functions about cluster were capitalized the wrong way.
-
由 antirez 提交于
-
由 antirez 提交于
See the top-comment for the function in this commit for details about what the function is supposed to do.
-
由 antirez 提交于
This is similar to getKeysInSlot() but just returns the number of keys found in a given hash slot, without returning the keys.
-
- 23 2月, 2013 5 次提交
-
-
由 antirez 提交于
-
由 antirez 提交于
-
由 antirez 提交于
The definition of cluster size is: the number of known nodes in the cluster that are masters and serving at least an hash slot.
-
由 antirez 提交于
-
由 antirez 提交于
A §Redis Cluster node used to mark a node as failing when itself detected a failure for that node, and a single acknowledge was received about the possible failure state. The new API will be used in order to possible to require that N other nodes have a PFAIL or FAIL state for a given node for a node to set it as failing.
-
- 22 2月, 2013 7 次提交
- 21 2月, 2013 11 次提交
- 20 2月, 2013 2 次提交
- 16 2月, 2013 1 次提交
-
-
由 antirez 提交于
-
- 15 2月, 2013 4 次提交