Skip to content

Commit 02aef1f

Browse files
committed
Doc fixes for restarting changes
1 parent a0fdb69 commit 02aef1f

File tree

1 file changed

+10
-10
lines changed
  • docs-source/content/userguide/managing-domains/domain-lifecycle

1 file changed

+10
-10
lines changed

docs-source/content/userguide/managing-domains/domain-lifecycle/restarting.md

Lines changed: 10 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -200,13 +200,13 @@ If you've created a new image that is not rolling compatible, and you've changed
200200

201201
In these cases, you must manually initiate a restart.
202202

203-
* **Managed Coherence Server safe shutdown**.
204-
205-
If the domain is configured to use Coherence Clusters, then you will need to increase the Kubernetes graceful timeout value.
206-
When a server is shutdown, Coherence needs time to recover partitions and rebalance the cluster before it is safe to shutdown a second server.
207-
Using the Kubernetes graceful termination feature, the Operator will automatically wait until the Coherence HAStatus MBean attribute
208-
indicates that it is safe to shutdown the server. However, once graceful termination timeout expires, the pod will be deleted regardless.
209-
Therefore, it is important to set the domain yaml timeoutSeconds to a large enough value to prevent the server from shutting down before
210-
Coherence is safe. Furthermore, if the Operator is not able to access the Coherence MBean then the server will not be shutdown
211-
until the domain timeoutSeconds expires. To minimize any possibility of cache data loss, you should increase the timeoutSeconds
212-
value to a large number, for example: 15 minutes.
203+
* **Managed Coherence Servers safe shutdown**.
204+
205+
If the domain is configured to use a Coherence cluster, then you will need to increase the Kubernetes graceful timeout value.
206+
When a server is shut down, Coherence needs time to recover partitions and rebalance the cluster before it is safe to shut down a second server.
207+
Using the Kubernetes graceful termination feature, the operator will automatically wait until the Coherence HAStatus MBean attribute
208+
indicates that it is safe to shut down the server. However, after the graceful termination timeout expires, the pod will be deleted regardless.
209+
Therefore, it is important to set the domain YAML `timeoutSeconds` to a large enough value to prevent the server from shutting down before
210+
Coherence is safe. Furthermore, if the operator is not able to access the Coherence MBean, then the server will not be shut down
211+
until the domain `timeoutSeconds` expires. To minimize any possibility of cache data loss, you should increase the `timeoutSeconds`
212+
value to a large number, for example, 15 minutes.

0 commit comments

Comments
 (0)