From: Dylan Whyte <d.whyte@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH pve-docs 6/6] fix 3375: warn user to remove replication jobs
Date: Wed, 15 Sep 2021 15:36:18 +0200 [thread overview]
Message-ID: <20210915133618.143859-6-d.whyte@proxmox.com> (raw)
In-Reply-To: <20210915133618.143859-1-d.whyte@proxmox.com>
this adds a warning in the documentation to remove any replication jobs
before deleting a cluster node
Signed-off-by: Dylan Whyte <d.whyte@proxmox.com>
---
pvecm.adoc | 14 +++++++++++---
1 file changed, 11 insertions(+), 3 deletions(-)
diff --git a/pvecm.adoc b/pvecm.adoc
index e7140a6..0b1857e 100644
--- a/pvecm.adoc
+++ b/pvecm.adoc
@@ -304,9 +304,17 @@ Remove a Cluster Node
CAUTION: Read the procedure carefully before proceeding, as it may
not be what you want or need.
-Move all virtual machines from the node. Make sure you have made copies of any
-local data or backups that you want to keep. In the following example, we will
-remove the node hp4 from the cluster.
+Move all virtual machines from the node. Ensure that you have made copies of any
+local data or backups that you want to keep. In addition, make sure to remove
+any scheduled replication jobs to the node to be removed.
+
+CAUTION: Failure to remove replication jobs to a node before removing said node
+will result in the replication job becoming irremovable. Especially note that
+replication automatically switches direction if a replicated VM is migrated, so
+by migrating a replicated VM from a node to be deleted, replication jobs will be
+set up to that node automatically.
+
+In the following example, we will remove the node hp4 from the cluster.
Log in to a *different* cluster node (not hp4), and issue a `pvecm nodes`
command to identify the node ID to remove:
--
2.30.2
next prev parent reply other threads:[~2021-09-15 13:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-15 13:36 [pve-devel] [PATCH pve-docs 1/6] pvecm: language and format fixup Dylan Whyte
2021-09-15 13:36 ` [pve-devel] [PATCH pve-docs 2/6] pvecm: replace {PVE} with {pve} Dylan Whyte
2021-09-15 13:36 ` [pve-devel] [PATCH pve-docs 3/6] pvecm: fix command output formatting Dylan Whyte
2021-09-15 13:36 ` [pve-devel] [PATCH pve-docs 4/6] pvecm: update instructions to add redundant links Dylan Whyte
2021-09-15 13:36 ` [pve-devel] [PATCH pve-docs 5/6] pvecm: add note about corosync killnode error Dylan Whyte
2021-09-16 8:04 ` Fabian Ebner
2021-09-15 13:36 ` Dylan Whyte [this message]
2021-09-15 15:03 ` [pve-devel] applied-series: [PATCH pve-docs 1/6] pvecm: language and format fixup Thomas Lamprecht
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210915133618.143859-6-d.whyte@proxmox.com \
--to=d.whyte@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox