Add nomad operator command for interacting with Raft configuration #2305
Conversation
this guarantees the nav list fits in this viewport range (there was a very small range where it broke the layout)
| ## Usage | ||
|
|
||
| ``` | ||
| nomad operator raft list-peers [options] |
There was a problem hiding this comment.
None of the other pages have that.
| nomad-server03.global 10.10.11.7:4647 10.10.11.7:4647 follower true | ||
| ``` | ||
|
|
||
| * `Node` is the node name of the server, as known to Nomad, or "(unknown)" if |
There was a problem hiding this comment.
For consistency, itd be great if we could use - instead of * for bullets.
| ## Usage | ||
|
|
||
| ``` | ||
| nomad operator raft remove-peer [options] |
| all Raft log entries, so should only be used to recover from an outage, but it | ||
| should allow recovery from any situation where there's some cluster data available. | ||
|
|
||
| <a name="peers.json"></a> |
There was a problem hiding this comment.
You don't need to do this - there will be an automatic <a> link generated as #manual-recovery-using-peers.json
| requires an operator to intervene, but the process is straightforward. | ||
|
|
||
| ~> This guide is for recovery from a Nomad outage due to a majority | ||
| of server nodes in a datacenter being lost. If you are just looking to |
|
|
||
| ```javascript | ||
| [ | ||
| "10.0.1.8:4647", |
There was a problem hiding this comment.
Two space before all these strings
|
@sethvargo Yeah docs/cluster -> guides/cluster is the only redirect! Thanks for review |
|
@dadgar perfect - ping me once these changes are out (can't put it out until then) and we'll get the redirs in place |
|
I'm going to lock this pull request because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active contributions. |
This PR adds:
nomad operator raft list-peersandnomad operator raft remove-peersubcommands@sethvargo For guidance on redirects from the old bootstrap page