diff options
| author | antirez <antirez@gmail.com> | 2010-04-22 20:24:00 +0200 |
|---|---|---|
| committer | antirez <antirez@gmail.com> | 2010-04-22 20:24:00 +0200 |
| commit | 7accafbbe22cbc46d5838c0288aacfce7ad2e0dc (patch) | |
| tree | 6e4adab0907e97a921a1a65d4e123097618bacf0 | |
| parent | ffcc5608aa194e5c86b44fb9a770429f3d9db8ae (diff) | |
| download | redis-7accafbbe22cbc46d5838c0288aacfce7ad2e0dc.tar.gz | |
typo fixed, reloaded
| -rw-r--r-- | design-documents/REDIS-CLUSTER | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/design-documents/REDIS-CLUSTER b/design-documents/REDIS-CLUSTER index 086acbf76..28b95ae50 100644 --- a/design-documents/REDIS-CLUSTER +++ b/design-documents/REDIS-CLUSTER @@ -55,10 +55,10 @@ and refusing any further query. The system administrator should check why M-1 nodes are offline and bring them back again if possible. Once resisting to big net splits is no longer a requirement as there is no -conflict resolution stage, since at least an original node responsible to hold -every possible key must be online for the cluster to work, there is also no need -a design where every node can act as an independent entity receiving queries -and forwarding this queries to other nodes as needed. +conflict resolution stage, since at least an original node responsible of +holding every possible key must be online for the cluster to work, there is +also no need for a design where every node can act as an independent entity +receiving queries and forwarding this queries to other nodes as needed. Instead a more decoupled approach can be used, in the form of a Redis Proxy node (or multiple Proxy nodes) that is contacted by clients, and |