Why Coherence Cache Services Are Leaving The Cluster When Used off-heap Backing-Map-Scheme?
(Doc ID 2572069.1)
Last updated on AUGUST 10, 2020
Applies to:Oracle Coherence - Version 126.96.36.199.0 and later
Information in this document applies to any platform.
Qn1: As per the <Note 2121757.1>, if we specify m for high-units 350m, it will not be honored. You should not specify m or g. You should specify as 350. Is that right? When should be "m"/"g" used for high-units?
Qn2: User has set the backup count to 2, backup storage limit to 350 MB and cache limit to 350 MB as well. Can you explain how this will work in terms of NIO buffer allocation and if the backup storage is set incorrectly to 350 MB instead of 2*350 = 700 MB?
Qn3: User also observe that after running for 12-15 hours the RSS memory consumed is close to 9G on a 16 server whereas VSZ memory is close to 11G. How will this impact Coherence and is coherence resilient enough to identify when it runs out direct buffer memory and evict expired partitions instead of giving OOM?
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document