이 콘텐츠는 선택한 언어로 제공되지 않습니다.
Chapter 5. Adjusting Container Specifications
You can allocate CPU and memory resources, specify JVM options, and configure storage for Data Grid nodes.
5.1. JVM, CPU, and Memory Resources 링크 복사링크가 클립보드에 복사되었습니다!
When Data Grid Operator creates Data Grid clusters, it uses spec.container.cpu
and spec.container.memory
to:
-
Ensure that OpenShift has sufficient capacity to run the Data Grid node. By default Data Grid Operator requests 512Mi of
memory
and 0.5cpu
from the OpenShift scheduler. -
Constrain node resource usage. Data Grid Operator sets the values of
cpu
andmemory
as resource limits.
Garbage collection logging
By default, Data Grid Operator does not log garbage collection (GC) messages. You can optionally add the following JVM options to direct GC messages to stdout:
extraJvmOpts: "-Xlog:gc*:stdout:time,level,tags"
extraJvmOpts: "-Xlog:gc*:stdout:time,level,tags"
5.2. Storage Resources 링크 복사링크가 클립보드에 복사되었습니다!
- 1
- Configures the storage size for Data Grid service nodes.
By default, Data Grid Operator allocates 1Gi
for storage for both Cache service and Data Grid service nodes. You can configure storage size only for Data Grid service nodes.
Persistence
Data Grid service lets you configure Single File cache stores for data persistence:
<persistence> <file-store /> </persistence>
<persistence>
<file-store />
</persistence>
5.2.1. Persistent Volume Claims 링크 복사링크가 클립보드에 복사되었습니다!
Data Grid Operator mounts persistent volumes at:/opt/datagrid/server/data
Persistent volume claims use the ReadWriteOnce (RWO)
access mode.