-
Notifications
You must be signed in to change notification settings - Fork 296
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
fix links in 3.3 #448
fix links in 3.3 #448
Conversation
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.
LGTM
See inlined comment for one small change.
Let's chat before you work on the next etcd version section.
Thanks for working on these @kapunahelewong! |
@@ -6,7 +6,7 @@ title: Clustering Guide | |||
|
|||
Starting an etcd cluster statically requires that each member knows another in the cluster. In a number of cases, the IPs of the cluster members may be unknown ahead of time. In these cases, the etcd cluster can be bootstrapped with the help of a discovery service. | |||
|
|||
Once an etcd cluster is up and running, adding or removing members is done via [runtime reconfiguration][runtime-conf]. To better understand the design behind runtime reconfiguration, we suggest reading [the runtime configuration design document][runtime-reconf-design]. | |||
Once an etcd cluster is up and running, adding or removing members is done via [runtime reconfiguration][runtime-conf]. To better understand the design behind runtime reconfiguration, we suggest reading [the runtime configuration design document][../../runtime-reconf-design]. |
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.
Oops, missed this the first time around: this link shouldn't have been changed. The link definition is fixed below in line 495.
So just revert the change to this line.
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.
See two inlined comments (I missed those earlier)
@@ -6,7 +6,7 @@ etcd comes with support for incremental runtime reconfiguration, which allows us | |||
|
|||
Reconfiguration requests can only be processed when a majority of cluster members are functioning. It is **highly recommended** to always have a cluster size greater than two in production. It is unsafe to remove a member from a two member cluster. The majority of a two member cluster is also two. If there is a failure during the removal process, the cluster might not be able to make progress and need to [restart from majority failure][majority failure]. | |||
|
|||
To better understand the design behind runtime reconfiguration, please read [the runtime reconfiguration document][runtime-reconf]. | |||
To better understand the design behind runtime reconfiguration, please read [the runtime reconfiguration document][../../runtime-reconf]. |
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.
Ditto, missed this the first time around: this link shouldn't have been changed. Revert the change to this line, and change the definition of [runtime-reconf]
on line 175 below.
FYI, I used this diff command over the generated site to find the broken links: $ git diff -I '^<meta \w+="[^"]*(date|time)' -I '>Last modified' -- . ':(exclude)*.xml' > ~/tmp/diff.txt
$ grep -e ^diff ~/tmp/diff.txt
diff --git a/docs/v3.3/branch_management/index.html b/docs/v3.3/branch_management/index.html
diff --git a/docs/v3.3/install/index.html b/docs/v3.3/install/index.html
diff --git a/docs/v3.3/op-guide/clustering/index.html b/docs/v3.3/op-guide/clustering/index.html
diff --git a/docs/v3.3/op-guide/runtime-configuration/index.html b/docs/v3.3/op-guide/runtime-configuration/index.html
diff --git a/docs/v3.3/platforms/aws/index.html b/docs/v3.3/platforms/aws/index.html |
This PR fixes the broken links in v3.3 as per #419