From 445b584333ff5bbf4e778b7a6805134746b473f7 Mon Sep 17 00:00:00 2001 From: Rob Szumski Date: Wed, 5 Feb 2014 16:52:31 -0800 Subject: [PATCH] fix(docs): explicitly create links instead of using the markdown parser --- Documentation/cluster-discovery.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/Documentation/cluster-discovery.md b/Documentation/cluster-discovery.md index 7be7b769c..c49dabcf4 100644 --- a/Documentation/cluster-discovery.md +++ b/Documentation/cluster-discovery.md @@ -8,7 +8,7 @@ Starting an etcd cluster can be painful since each node needs to know of another ### Create a Token -To use the discovery API, you must first create a token for your etcd cluster. Visit https://discovery.etcd.io/new to create a new token. +To use the discovery API, you must first create a token for your etcd cluster. Visit [https://discovery.etcd.io/new](https://discovery.etcd.io/new) to create a new token. You can inspect the list of peers by viewing `https://discovery.etcd.io/`. @@ -26,7 +26,7 @@ TOKEN=$(curl https://discovery.etcd.io/new) ## Running Your Own Discovery Endpoint -The discovery API communicates with a separate etcd cluster to store and retrieve the list of peers. CoreOS provides https://discovery.etcd.io as a free service, but you can easily run your own etcd cluster for this purpose. Here's an example using an etcd cluster located at `10.10.10.10:4001`: +The discovery API communicates with a separate etcd cluster to store and retrieve the list of peers. CoreOS provides [https://discovery.etcd.io](https://discovery.etcd.io) as a free service, but you can easily run your own etcd cluster for this purpose. Here's an example using an etcd cluster located at `10.10.10.10:4001`: ``` TOKEN="testcluster" @@ -42,4 +42,4 @@ The Discovery API submits the `-peer-addr` of each etcd instance to the configur ## Stale Peers -The discovery API will automatically clean up the address of a stale peer that is no longer part of the cluster. The TTL for this process is a week, which should be long enough to handle any extremely long outage you may encounter. There is no harm in having stale peers in the list until they are cleaned up, since an etcd instance only needs to connect to one valid peer in the cluster to join. \ No newline at end of file +The discovery API will automatically clean up the address of a stale peer that is no longer part of the cluster. The TTL for this process is a week, which should be long enough to handle any extremely long outage you may encounter. There is no harm in having stale peers in the list until they are cleaned up, since an etcd instance only needs to connect to one valid peer in the cluster to join.