-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
docs: add explanation of modes #74
Conversation
Client have to read whole response bodies if they want the advantage of reusing TCP connections. https://code.google.com/p/go/source/detail?r=d4e1ec84876c0f5611ab86a03826da14b866efb2&name=release-branch.go1.1&path=/src/pkg/net/http/transport.go
To be more readable and get rid of false error message.
server: don't print out errors that cannot be resolved
server: remove panic or fatal in participant.run
*: rename etcd to etcdserver
etcd: add consistent get
etcdserver: rename someMachineMessage->machineMessage
wal: move record method to record.go
conf: remove GraphiteHost flag
etcdserver: use snapshotCount flag
|
||
### Standby Mode | ||
|
||
Standby-mode node proxies all requests to participant-mode nodes, and joins cluster if needed. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Standby-mode machines proxy all requests to participant-mode machines and join the cluster if there is space for more participants.
refreshed. |
@@ -0,0 +1,25 @@ | |||
## Modes | |||
|
|||
Etcd runs in either participant mode or standby mode. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
etcd not Etcd
We don't have standby anymore. Close this one. |
No description provided.