Termination Of PartitionedCache Due To Unhandled Exception Due to Latency In The Cluster Communications.
(Doc ID 2572048.1)
Last updated on SEPTEMBER 18, 2023
Applies to:
Oracle Coherence - Version 12.2.1.3.0 and laterInformation in this document applies to any platform.
Symptoms
User reported that our architecture consists of 3 physical machines, each of which contain 8 Coherence Storage Enabled JVMs, so in total we have 24 JVMs split equally into 3 machines. Those 24 JVMs are logically are also split into 4 logical groups (JVMs of the same group have the same attribute and difference cache configurations), each of which contain 6 Storage Enabled JVMs. The issue arose when one of the physical machines restarted due to human error. After the physical machine went down, the other two physical machines experienced high CPU load and high G1GC times for their JVMs, as expected. The unexpected behavior started to happen, at that time, a PartitionLostEvent was caught and we lost data from only one of the Cache Services of this specific logical group.
Changes
Cause
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
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |