Skip to content

Commit 24d5e8d

Browse files
committed
Merge remote-tracking branch 'origin/main' into release/4.0
2 parents 7345c91 + 75f6813 commit 24d5e8d

File tree

4 files changed

+18
-0
lines changed

4 files changed

+18
-0
lines changed

documentation/4.0/content/faq/resource-settings.md

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -199,6 +199,13 @@ There's no memory or CPU limit configured by default in samples and so the defau
199199

200200
If you wish to set resource requests or limits differently on a sample Domain or Cluster YAML file or template, see [Setting resource requests and limits in a Domain or Cluster resource](#setting-resource-requests-and-limits-in-a-domain-or-cluster-resource). Or, for samples that generate their Domain resource using an "inputs" YAML file, see the `serverPodMemoryRequest`, `serverPodMemoryLimit`, `serverPodCpuRequest`, and `serverPodCpuLimit` parameters in the sample's `create-domain.sh` inputs file.
201201

202+
#### Burstable pods and JDK active processor count calculation
203+
If you have [Burstable Pods](https://kubernetes.io/docs/tasks/configure-pod-container/quality-service-pod/#create-a-pod-that-gets-assigned-a-qos-class-of-burstable) that configure the CPU resource requests but have no CPU limits, then the JDK can incorrectly calculate the active processor count. The JDK interprets the value of the `--cpu-shares` parameter (which maps to `spec.containers[].resources.requests.cpu`) to limit how many CPUs the current process can use, as explained in [JDK-8288367](https://bugs.openjdk.org/browse/JDK-8288367). This might cause the JVM to use fewer CPUs than available, leading to an under utilization of CPU resources when running in a Kubernetes environment. Updating the JDK to newer versions, `JDK 8u371` or `JDK 11.0.17`, fixes this.
204+
205+
{{% notice note %}}
206+
To override the number of CPUs that the JVM automatically detects and uses when creating threads for various subsystems, use the `-XX:ActiveProcessorCount` Java option.
207+
{{% /notice %}}
208+
202209
#### Configuring CPU affinity
203210

204211
A Kubernetes hosted WebLogic Server may exhibit high lock contention in comparison to an on-premises deployment. This lock contention may be due to a lack of CPU cache affinity or scheduling latency when workloads move between different CPU cores.

documentation/4.0/content/release-notes.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -124,6 +124,8 @@ draft: false
124124
* Added `.spec.configuration.model.auxiliaryImages` for simplified configuration of auxiliary images.
125125
* Added several additional advanced settings related to auxiliary images including `.spec.configuration.model.auxiliaryImageVolumeMountPath`, `.spec.configuration.model.auxiliaryImageVolumeMedium`, and `.spec.configuration.model.auxiliaryImageVolumeSizeLimit`.
126126
* Removed `.spec.serverPod.auxiliaryImages` and `.spec.auxiliaryImageVolumes` as part of the simplification effort.
127+
* Default change for `domain.spec.configuration.model.wdtInstallHome` to `/aux/weblogic-deploy` if `spec.configuration.model.AuxiliaryImages` are specified, and to `/u01/wdt/weblogic-deploy` otherwise. It previously always defaulted to `/u01/wdt/weblogic-deploy`.
128+
* Default change for `domain.spec.configuration.model.wdtModelHome` to `/aux/models` if `spec.configuration.model.AuxiliaryImages` are specified, and to `/u01/wdt/models` otherwise. It previously always defaulted to `/u01/wdt/models`.
127129

128130
* Cluster changes.
129131
* Moved content under `.spec.clusters[*]` to the new Cluster resource `.spec`.

kubernetes/charts/weblogic-operator/templates/_operator-dep.tpl

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -46,6 +46,10 @@ spec:
4646
affinity:
4747
{{- toYaml . | nindent 8 }}
4848
{{- end }}
49+
{{- with .tolerations }}
50+
tolerations:
51+
{{- toYaml . | nindent 8 }}
52+
{{- end }}
4953
containers:
5054
- name: "weblogic-operator"
5155
image: {{ .image | quote }}

kubernetes/charts/weblogic-operator/values.yaml

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -182,6 +182,11 @@ preserveWebhook: false
182182
# for more information on affinity and anti-affinity.
183183
#affinity:
184184

185+
# tolerations and taints work together to ensure that pods are not scheduled on inappropriate nodes. If the tolerations value is specified,
186+
# then this content will be added to the operator's deployment. See https://kubernetes.io/docs/concepts/scheduling-eviction/taint-and-toleration/
187+
# for more information on tolerations and taints.
188+
#tolerations:
189+
185190
# Values related to debugging the operator.
186191
# Customers should not need to use the following properties
187192

0 commit comments

Comments
 (0)