Red Hat SummitEste conteúdo não está disponível no idioma selecionado.
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
spec:
...
container:
extraJvmOpts: "-XX:NativeMemoryTracking=summary" 1
cpu: "1000m" 2
memory: 1Gi 3
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
memoryand 0.5cpufrom the OpenShift scheduler. -
Constrain node resource usage. Data Grid Operator sets the values of
cpuandmemoryas 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"
5.2. Storage Resources
spec:
...
service:
type: DataGrid
container:
storage: 2Gi 1- 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>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.
