luxolus
/
open-nomad
2
0
Fork 0
Code Issues 1 Pull Requests Packages Releases Wiki Activity

docs: fix broken links

This commit is contained in:
Michael Schurter 2018-04-12 17:28:26 -07:00
parent cbbabadddb
commit be86ee4025
4 changed files with 10 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
website/source/docs/job-specification/reschedule.html.md
View File

@ -112,7 +112,7 @@ defaults by job type:
### Rescheduling during deployments
The [update stanza](docs/job-specification/update.html) controls rolling updates and canary deployments. A task
The [update stanza](/docs/job-specification/update.html) controls rolling updates and canary deployments. A task
group's reschedule stanza does not take affect during a deployment. For example, if a new version of the job
is rolled out and the deployment failed due to a failing allocation, Nomad will not reschedule it.

2
website/source/docs/operating-a-job/failure-handling-strategies/index.html.md
View File

@ -22,4 +22,4 @@ Please see one of the guides below or use the navigation on the left for details
1. [Local Restarts](/docs/operating-a-job/failure-handling-strategies/restart.html)
1. [Check Restarts](/docs/operating-a-job/failure-handling-strategies/check-restart.html)
1. [Rescheduling](/docs/operating-a-job/failure-handling-strategies/rescheduling.html)
1. [Rescheduling](/docs/operating-a-job/failure-handling-strategies/reschedule.html)

12
website/source/docs/upgrade/upgrade-specific.html.md
View File

@ -19,11 +19,13 @@ standard upgrade flow.
### Raft Protocol Version Compatibility
When upgrading to Nomad 0.8.0 from a version lower than 0.7.0, users will need to
set the [`-raft-protocol`](/docs/agent/options.html#_raft_protocol) option to 1 in
order to maintain backwards compatibility with the old servers during the upgrade.
After the servers have been migrated to version 0.8.0, `-raft-protocol` can be moved
up to 2 and the servers restarted to match the default.
When upgrading to Nomad 0.8.0 from a version lower than 0.7.0, users will need
to set the
[`raft_protocol`](/docs/agent/configuration/server.html#raft_protocol) option
in their `server` stanza to 1 in order to maintain backwards compatibility with
the old servers during the upgrade. After the servers have been migrated to
version 0.8.0, `raft_protocol` can be moved up to 2 and the servers restarted
to match the default.
The Raft protocol must be stepped up in this way; only adjacent version numbers are
compatible (for example, version 1 cannot talk to version 3). Here is a table of the

2
website/source/guides/ui.html.md
View File

@ -156,7 +156,7 @@ for pausing and playing log streaming, jumping to the head or tail of the log, a
[![Task Logs][img-task-logs]][img-task-logs]
~> **Note.** Only `stdout` and `stderr` are available in the UI. Any logs written to a file are available from the
~> CLI using the [`nomad alloc fs`]('/docs/commands/alloc/fs.html'), but filesystem access is not yet in the Web UI.
~> CLI using the [`nomad alloc fs`](/docs/commands/alloc/fs.html), but filesystem access is not yet in the Web UI.
## Reviewing Clients