Skip to content

Commit c64b769

Browse files
committed
Slight tweaks to start/stop doc
1 parent bbcf4dd commit c64b769

File tree

1 file changed

+6
-7
lines changed

1 file changed

+6
-7
lines changed

site/server-lifecycle.md

Lines changed: 6 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -14,13 +14,13 @@ The operator runtime monitors this property and creates or deletes the correspon
1414
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").
1515
The "restartVersion" property on the domain resource lets the user force the operator to restart a set of server pods.
1616

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.
1818
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.
1919
By default, the servers are restarted one at a time.
2020

2121
## Starting and Stopping Servers
2222

23-
### serverStartPolicy rules
23+
### "serverStartPolicy" Rules
2424

2525
The "serverStartPolicy" property determine which servers should be running.
2626

@@ -44,7 +44,7 @@ A clustered managed server will be started if:
4444
* AND
4545
* the cluster is "IF_NEEDED" (I.e. not "NEVER")
4646
* 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
4848

4949
### Common Scenarios
5050

@@ -62,7 +62,6 @@ For example:
6262

6363
#### Shut Down All the Servers
6464
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":
6665
```
6766
domain:
6867
spec:
@@ -80,7 +79,7 @@ Sometimes the user wants to only start the admin server, that is, take the domai
8079
```
8180

8281
#### 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".
8483
```
8584
domain:
8685
spec:
@@ -102,8 +101,8 @@ To shut down a specific stand alone server, add it to the domain resource and se
102101
```
103102

104103
#### 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.
107106

108107
This is done by adding the server to the domain resource and settings its "serverStartPolicy" to "ALWAYS".
109108
```

0 commit comments

Comments
 (0)