fluencelabs/redis
1
0
Fork 0
mirror of https://github.com/fluencelabs/redis synced 2025-03-19 17:10:50 +00:00
Code Issues Projects Releases Wiki Activity

typo fixed, reloaded

Browse Source
This commit is contained in:
antirez 2010-04-22 20:24:00 +02:00
parent ffcc5608aa
commit 7accafbbe2
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
design-documents/REDIS-CLUSTER
View File

@ -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