From 25e8eb596ffbe5ac41f35f825c72d640949537bd Mon Sep 17 00:00:00 2001 From: Bob Date: Thu, 4 Mar 2021 11:38:45 -0500 Subject: [PATCH] ISSUE-27701 - Minor edit for emphasis --- modules/storage-multi-attach-error.adoc | 2 +- modules/storage-persistent-storage-pv.adoc | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/modules/storage-multi-attach-error.adoc b/modules/storage-multi-attach-error.adoc index e9946dadb5a0..20bd289bd422 100644 --- a/modules/storage-multi-attach-error.adoc +++ b/modules/storage-multi-attach-error.adoc @@ -30,7 +30,7 @@ For most storage solutions, you can use ReadWriteMany (RWX) volumes to prevent m + For storage that does not support RWX, such as VMware vSphere, RWO volumes must be used instead. However, RWO volumes cannot be mounted on multiple nodes. + -If you encounter a multi-attach error message with an RWO volume, force delete the pod on a shut down or crashed node. +If you encounter a multi-attach error message with an RWO volume, force delete the pod on a shutdown or crashed node to avoid data loss in critical workloads, such as when dynamic persistent volumes are attached. + [source,terminal] ---- diff --git a/modules/storage-persistent-storage-pv.adoc b/modules/storage-persistent-storage-pv.adoc index 88a17ec9e5ea..41d32fafb74c 100644 --- a/modules/storage-persistent-storage-pv.adoc +++ b/modules/storage-persistent-storage-pv.adoc @@ -160,7 +160,7 @@ endif::[] |=== [.small] -- -1. ReadWriteOnce (RWO) volumes cannot be mounted on multiple nodes. If a node fails, the system does not allow the attached RWO volume to be mounted on a new node because it is already assigned to the failed node. If you encounter a multi-attach error message as a result, force delete the pod on a shut down or crashed node. +1. ReadWriteOnce (RWO) volumes cannot be mounted on multiple nodes. If a node fails, the system does not allow the attached RWO volume to be mounted on a new node because it is already assigned to the failed node. If you encounter a multi-attach error message as a result, force delete the pod on a shutdown or crashed node to avoid data loss in critical workloads, such as when dynamic persistent volumes are attached. 2. Use a recreate deployment strategy for pods that rely on AWS EBS. // GCE Persistent Disks, or Openstack Cinder PVs. --