Hello World

Documentation/README.md

@@ -3,3 +3,4 @@
 etcd is a distributed key-value store designed to reliably and quickly preserve and provide access to critical data. It enables reliable distributed coordination through distributed locking, leader elections, and write barriers. An etcd cluster is intended for high availability and permanent data storage and retrieval.
 
 Please note that the files in this directory are *source files* for the built and rendered documentation that can be viewed at [etcd.io/docs](https://etcd.io/docs).Hello World 2
+Hello World

Documentation/benchmarks/README.md

@@ -17,3 +17,4 @@ It records expected memory usage in different scenarios.
 [2.2-mem]: etcd-2-2-0-rc-memory-benchmarks.md
 [3.0]: etcd-3-demo-benchmarks.md
 Hello World 2
+Hello World

Documentation/etcd-mixin/README.md

@@ -24,3 +24,4 @@ Then run the unit test:
 promtool test rules test.yaml
 ```
 Hello World 2
+Hello World

Documentation/learning/lock/README.md

@@ -60,3 +60,4 @@ failed to write to storage: error: given version (4703569812595502721) differ fr
 [unsafe-lock]: https://martin.kleppmann.com/2016/02/unsafe-lock.png
 [fencing-tokens]: https://martin.kleppmann.com/2016/02/fencing-tokens.png
 Hello World 2
+Hello World

README.md

@@ -207,3 +207,4 @@ These emeritus maintainers dedicated a part of their career to etcd and reviewed
 
 etcd is under the Apache 2.0 license. See the [LICENSE](LICENSE) file for details.
 Hello World 2
+Hello World

client/README.md

@@ -111,3 +111,4 @@ if err != nil {
 
 4. etcd/client cannot detect whether a member is healthy with watches and non-quorum read requests. If the member is isolated from the cluster, etcd/client may retrieve outdated data. Instead, users can either issue quorum read requests or monitor the /health endpoint for member health information.
 Hello World 2
+Hello World

clientv3/README.md

@@ -84,3 +84,4 @@ Client request size limit is configurable via `clientv3.Config.MaxCallSendMsgSiz
 
 More code examples can be found at [GoDoc](https://godoc.org/go.etcd.io/etcd/clientv3).
 Hello World 2
+Hello World

contrib/README.md

@@ -7,3 +7,4 @@ Scripts and files which may be useful but aren't part of the core etcd project.
 * [systemd/etcd2-backup-coreos](systemd/etcd2-backup-coreos) - remote backup and restore procedures for etcd2 clusters on CoreOS Linux
 * [systemd/etcd3-multinode](systemd/etcd3-multinode) - multi-node cluster setup with systemd
 Hello World 2
+Hello World

contrib/raftexample/README.md

@@ -124,3 +124,4 @@ When raft reaches a consensus, the server publishes all committed updates over a
 For raftexample, this commit channel is consumed by the key-value store.
 
 Hello World 2
+Hello World

contrib/systemd/etcd3-multinode/README.md

@@ -172,3 +172,4 @@ sudo systemctl stop my-etcd-3.service
 sudo systemctl disable my-etcd-3.service
 ```
 Hello World 2
+Hello World

etcdctl/README.md

@@ -1686,3 +1686,4 @@ backward compatibility for `JSON` format and the format in non-interactive mode.
 [etcdrpc]: ../etcdserver/etcdserverpb/rpc.proto
 [storagerpc]: ../mvcc/mvccpb/kv.proto
 Hello World 2
+Hello World

functional/README.md

@@ -217,3 +217,4 @@ $ curl -L http://localhost:1381/blackhole-rx -X PUT
 # s1 becomes follower after election timeout
 ```
 Hello World 2
+Hello World

hack/README.md

@@ -1,2 +1,3 @@
 Various hacks that are used by developers.
 Hello World 2
+Hello World

hack/benchmark/README.md

@@ -13,3 +13,4 @@ Benchmark 3-member etcd cluster to get its read and write performance.
 1. Set environment variable `GOMAXPROCS` as the number of available cores to maximize CPU resources for both etcd member and bench process.
 2. Set the number of open files per process as 10000 for amounts of client connections for both etcd member and benchmark process.
 Hello World 2
+Hello World

hack/insta-discovery/README.md

@@ -1,2 +1,3 @@
 Starts a cluster via the discovery service locally. Useful for testing.
 Hello World 2
+Hello World

hack/kubernetes-deploy/README.md

@@ -20,3 +20,4 @@ TODO:
 - create a replication controller like service that knows how to add and remove nodes from the cluster correctly
 - use kubernetes secrets API to configure TLS for etcd clients and peers
 Hello World 2
+Hello World

hack/patch/README.md

@@ -36,3 +36,4 @@ To cherry pick 12345 then 56789 and propose them togther as a single PR, run:
 
 
 Hello World 2
+Hello World

hack/tls-setup/README.md

@@ -30,3 +30,4 @@ Example:
 ```
 3. Run `make` to generate the certs
 Hello World 2
+Hello World

pkg/README.md

@@ -1,3 +1,4 @@
 pkg/ is a collection of utility packages used by etcd without being specific to etcd itself. A package belongs here
 only if it could possibly be moved out into its own repository in the future.
 Hello World 2
+Hello World

pkg/adt/README.md

@@ -47,3 +47,4 @@ Deleting the node `11` triggers multiple rotates for rebalancing:
 
 Try yourself at https://www.cs.usfca.edu/~galles/visualization/RedBlack.html.
 Hello World 2
+Hello World

raft/README.md

@@ -196,3 +196,4 @@ To ensure there is no attempt to commit two membership changes at once by matchi
 
 This approach introduces a problem when removing a member from a two-member cluster: If one of the members dies before the other one receives the commit of the confchange entry, then the member cannot be removed any more since the cluster cannot make progress. For this reason it is highly recommended to use three or more nodes in every cluster.
 Hello World 2
+Hello World

security/README.md

@@ -32,3 +32,4 @@ As the security issue moves from triage, to identified fix, to release planning
 
 A public disclosure date is negotiated by the etcd Product Security Committee and the bug reporter. We prefer to fully disclose the bug as soon as possible once user mitigation is available. It is reasonable to delay disclosure when the bug or the fix is not yet fully understood, the solution is not well-tested, or for vendor coordination. The timeframe for disclosure is from immediate (especially if it's already publicly known) to a few weeks. As a basic default, we expect report date to disclosure date to be on the order of 7 days. The etcd Product Security Committee holds the final say when setting a disclosure date.
 Hello World 2
+Hello World

tools/benchmark/README.md

@@ -11,3 +11,4 @@ $ ls $GOPATH/bin
 benchmark
 ```
 Hello World 2
+Hello World

tools/etcd-dump-db/README.md

@@ -73,3 +73,4 @@ key="\x00\x00\x00\x00\x005@x_\x00\x00\x00\x00\x00\x00\x00\bt", value="\n\x153640
 key="\x00\x00\x00\x00\x005@x_\x00\x00\x00\x00\x00\x00\x00\at", value="\n\x153640412599896088633_7"
 ```
 Hello World 2
+Hello World

tools/etcd-dump-logs/README.md

@@ -132,3 +132,4 @@ Entry types () count is : 4
 ```
 [decoder_correctoutputformat.sh]: ./testdecoder/decoder_correctoutputformat.sh
 Hello World 2
+Hello World

tools/local-tester/README.md

@@ -24,3 +24,4 @@ The fault injected cluster is invoked with `goreman`:
 goreman -f tools/local-tester/Procfile start
 ```
 Hello World 2
+Hello World