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
+3-4Lines changed: 3 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -131,7 +131,7 @@ The `restartVersion` property on the domain resource lets you force the operator
131
131
The operator runtime does rolling restarts of clustered servers so that service is maintained.
132
132
133
133
### Properties that cause servers to be restarted
134
-
The operator will restart servers when any of the follow properties on the domain resource that affect the server, are changed:
134
+
The operator will restart servers when any of the follow properties on the domain resource that affect the server are changed:
135
135
*`annotations`
136
136
*`containerSecurityContext`
137
137
*`domainHome`
@@ -145,16 +145,15 @@ The operator will restart servers when any of the follow properties on the domai
145
145
*`logHomeEnabled`
146
146
*`logHome`
147
147
*`livenessProbe`
148
+
*`nodeSelector`
148
149
*`podSecurityContext`
149
150
*`readinessProbe`
151
+
*`resources`
150
152
*`restartVersion`
151
153
*`serverStartState`
152
154
*`volumes`
153
155
*`volumeMounts`
154
156
155
-
**Note**: The operator does not restart affected servers when `nodeSelector` or `resources` is changed on the domain resource.
156
-
In these cases, you can use `restartVersion` to force the operator to restart the servers.
157
-
158
157
### Rolling restarts
159
158
160
159
Clustered servers that need to be restarted are gradually restarted (for example, `rolling restarted`) so that the cluster is not taken out of service and in-flight work can be migrated to other servers in the cluster.
0 commit comments