Passivation impact on Storage size/Memory size in DG Operator in Openshift 4
Environment
- Red hat OpenShift Container Platform (OCP)
- 4.x
- Red Hat Data Grid (RHDG)
- 8.x
Issue
- Storage setting in Infinispan Custom Resource in DG Operator given passivation=false or true
- Storage size in DG Operator in Openshift 4
Resolution
When passivation=false it might be required to set the container size as much as the storage size. Because passivation=false implies everything goes into the store, depending on the eviction setting.
Whereas the opposite is true: when passivation=true, everything is either in memory or in the store, not both, depending on if it's been evicted.
Root Cause
The following settings matter for storage size allocation in DG (and therefore DG pod):
- eviction
- expiration
- passivation
About passivation:
| Passivation setting | Behavior |
|---|---|
| Passivation=false | Passivation equals false means everything goes into the store, meaning everything to memory and storage in with passivation=false |
| Passivation=true | Passivation equals true, only evicted entries go into the store |
Regarding eviction:
| Eviction | Beahvior |
|---|---|
| Eviction disabled | with no eviction everything is in both: memory and storage |
| Eviction enabled | with eviction, everything is in the store, and a subset (anything not evicted yet) is in memory |
Passivation == true behavior
With the normal passivation=true everything is either in memory or in the store, not both, depending on if it's been evicted.
See the solution DG 8 Persistence Volume details and how to read PV, for a more detailed review on PV.
Diagnostic Steps
- Verify Infinispan Custom Resource for storage and memory size
This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.