ReplicateAllPercentComplete Is Not Resetting To 0 On replicateAll() After A Prior Aborted Attempt.
(Doc ID 3064374.1)
Last updated on DECEMBER 26, 2024
Applies to:
Oracle Coherence - Version 12.2.1.4.0 and laterInformation in this document applies to any platform.
Symptoms
In the ECE Coherence cluster active-active deployment. Prior to starting a replicateAll, the ReplicateAllPercentComplete values were in the nn% range. Likely due to an aborted replicateAll which was aborted by stopping federation. When starting the replicateAll, the ReplicateAllPercentComplete values did not reset to 0. The resetStatistics() operation was performed on some of the member's destination MBeans which did reset ReplicateAllPercentComplete to zero. However, during the next replicateAll(), ReplicateAllPercentComplete did not reach nn+nn% for those members. We do not know if that is a problem with the metric, or an issue where replicateAll() was stuck. Based on cache sizes, the metric should have been around ~100%.
ReplicateAllPercentComplete is not resetting to 0 on replicateAll() after a prior aborted attempt.
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 |