coreos/etcd master into fork #1
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
fix(CONTRIBUTING.md): Fix title case
Clean up CONTRIBUTING.md and other bits of template-project
…"StartTime" Changed the LeaderInfo struct "start time" field from "startTime" to "StartTime" so that it is an exported identifier. This required adding the `json:"startTime"` structure field tag so that the encoding/json package correctly performs JSON encoding (i.e. the correct property name --> startTime).
"net/http".Error reset the content type, so we get rid of it and write our own one.
fix(docs): add information about standbys
Adding autodock into the libraries and tools section
docs(clustering): limit for peer-address changing
Standby server will switch to peer server if it finds that it has been contained in the cluster.
fix(standby_server): able to join the cluster containing itself
This one breaks because it doesn't set joinIndex correctly.
fix(server/v2): set correct content-type for etcdError response
fix(server): joinIndex is not set after recovery from full outage
docs(cluster-discovery): add caution to use old discovery endpoint
The cluster configuration operation is originally to make sure the instance won't be added back automatically between removal and check for the number of existing peer-mode instances. But this could make some node removed before the removal command. Use longer sync interval instead to avoid this problem.
fix(remove_node_test): remove unnecessary cluster configuration
chore(peer_server): improve log for auto removal
fix(peer_server) set content type to application/json in admin
Update optimal-cluster-size.md
Conflicts: CONTRIBUTING.md LICENSE
docs(cluster-size): remove outdated references to flag max-cluster-size
Many http clients will missbehave unless they get an initial http- response, even when long-polling. It also saves the user/client from having to handle headers on the first action of the watch, but rather handle the response immediately.
fix(server/server.go): /v2/stats endpoints emit application/json content type header
The default is for connections to last forever[1]. This leads to fds leaking. I set the timeout so high by default so that watches don't have to keep retrying but perhaps we should set it slower. Tested on a cluster with lots of clients and it seems to have relieved the problem. [1] https://groups.google.com/forum/#!msg/golang-nuts/JFhGwh1q9xU/heh4J8pul3QJ
URL is no longer working
etcd: add a read/write timeout to server
server: Flush headers when using wait=true and stream=true
feat(get): get from quorum
Added Access-Control-Allow-Headers for CORS requests
fix(docs): name defaults to uuid not hostname
Documentation: add note about consistent=true
jacksoncage
added a commit
that referenced
this pull request
Jul 15, 2014
coreos/etcd master into fork
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.