vitalif
/
etcd
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Broken link in runtime-configuration.md 

See the issue created here:
https://github.com/etcd-io/etcd/issues/10989#issuecomment-518726038

doc: fix broken links referring to etcd.redhatdocs.io

Adding links to internal Documentation within github.com.

Update runtime-configuration.md

Update runtime-configuration.md

Update CHANGELOG-3.3.md

Remove extra space

Keep the formatting similar to original
release-3.5
retroflexer 2019-08-06 14:14:32 -04:00
parent 44a00a33ef
commit 742f928c6a
2 changed files with 3 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
CHANGELOG-3.3.md
View File

@ -53,7 +53,7 @@ See [code changes](https://github.com/etcd-io/etcd/compare/v3.3.12...v3.3.13) an
### Metrics, Monitoring ### Metrics, Monitoring
See [List of metrics](https://etcd.readthedocs.io/en/latest/operate.html#v3-3) for all metrics per release. See [List of metrics](https://etcd.io/docs/v3.3.12/metrics/) for all metrics per release.
Note that any `etcd_debugging_*` metrics are experimental and subject to change. Note that any `etcd_debugging_*` metrics are experimental and subject to change.

3
Documentation/op-guide/runtime-configuration.md
View File

@ -126,7 +126,7 @@ If adding multiple members the best practice is to configure a single member at
#### Add a new member as learner #### Add a new member as learner
Starting from v3.4, etcd supports adding a new member as learner / non-voting member. Starting from v3.4, etcd supports adding a new member as learner / non-voting member.
The motivation and design can be found in [design doc](https://etcd.readthedocs.io/en/latest/server-learner.html). The motivation and design can be found in [design doc][design-learner].
In order to make the process of adding a new member safer, In order to make the process of adding a new member safer,
and to reduce cluster downtime when the new member is added, it is recommended that the new member is added to cluster and to reduce cluster downtime when the new member is added, it is recommended that the new member is added to cluster
as a learner until it catches up. This can be described as a three step process: as a learner until it catches up. This can be described as a three step process:
@ -243,3 +243,4 @@ It is enabled by default.
[remove member]: #remove-a-member [remove member]: #remove-a-member
[runtime-reconf]: runtime-reconf-design.md [runtime-reconf]: runtime-reconf-design.md
[error cases when promoting a member]: #error-cases-when-promoting-a-learner-member [error cases when promoting a member]: #error-cases-when-promoting-a-learner-member
[design-learner]: ../learning/design-learner.md