You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: site/server-lifecycle.md
+6-7Lines changed: 6 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,13 +14,13 @@ The operator runtime monitors this property and creates or deletes the correspon
14
14
The operator runtime automatically recreates (restarts) server pods when properties on the domain resource that affect server pods change (such as "image", "volumes" and "env").
15
15
The "restartVersion" property on the domain resource lets the user force the operator to restart a set of server pods.
16
16
17
-
The operator runtime does rolling restarts of clustered servers so that that service is maintained.
17
+
The operator runtime does rolling restarts of clustered servers so that service is maintained.
18
18
The "maxUnavailable" property determines how many of the cluster's servers may be taken out of service at a time when doing a rolling restart.
19
19
By default, the servers are restarted one at a time.
20
20
21
21
## Starting and Stopping Servers
22
22
23
-
### serverStartPolicy rules
23
+
### "serverStartPolicy" Rules
24
24
25
25
The "serverStartPolicy" property determine which servers should be running.
26
26
@@ -44,7 +44,7 @@ A clustered managed server will be started if:
44
44
* AND
45
45
* the cluster is "IF_NEEDED" (I.e. not "NEVER")
46
46
* AND
47
-
** the server is "ALWAYS", or if the server is "IF_NEEDED" and the operator needs to start it to get to the cluster's "replicas" count
47
+
* the server is "ALWAYS", or if the server is "IF_NEEDED" and the operator needs to start it to get to the cluster's "replicas" count
48
48
49
49
### Common Scenarios
50
50
@@ -62,7 +62,6 @@ For example:
62
62
63
63
#### Shut Down All the Servers
64
64
Sometimes the user needs to completely shut down the domain (i.e. take it out of service).
65
-
The simplest was to do this is to set the domain level "serverStartPolicy" to "NEVER":
66
65
```
67
66
domain:
68
67
spec:
@@ -80,7 +79,7 @@ Sometimes the user wants to only start the admin server, that is, take the domai
80
79
```
81
80
82
81
#### Shut Down A Cluster
83
-
To shut down a cluster, add it to the domain resource and set its "serverStartPolicy" to "NEVER"
82
+
To shut down a cluster (i.e. take it out of service), add it to the domain resource and set its "serverStartPolicy" to "NEVER".
84
83
```
85
84
domain:
86
85
spec:
@@ -102,8 +101,8 @@ To shut down a specific stand alone server, add it to the domain resource and se
102
101
```
103
102
104
103
#### Force a Specific Clustered Managed Server To Start
105
-
Normally, all of the managed servers in a cluster are identical and it doesn't matter which ones are run as long as the operator starts enough to get to the cluster's "replicas" count.
106
-
However, sometimes some of the managed servers might be different (e.g support some extra services that the other servers in the cluster use) and need to always to started.
104
+
Normally, all of the managed servers in a cluster are identical and it doesn't matter which ones are running as long as the operator starts enough to get to the cluster's "replicas" count.
105
+
However, sometimes some of the managed servers are different (e.g support some extra services that the other servers in the cluster use) and need to always to started.
107
106
108
107
This is done by adding the server to the domain resource and settings its "serverStartPolicy" to "ALWAYS".
0 commit comments