Skip to content
GitLab
Menu
Projects
Groups
Snippets
Loading...
Help
Help
Support
Community forum
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
Menu
Open sidebar
ruanhaishen
redis
Commits
7accafbb
Commit
7accafbb
authored
Apr 22, 2010
by
antirez
Browse files
typo fixed, reloaded
parent
ffcc5608
Changes
1
Hide whitespace changes
Inline
Side-by-side
design-documents/REDIS-CLUSTER
View file @
7accafbb
...
...
@@ -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
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
.
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment