Coherence Persistence Snapshot Is Triggered Impact On On-going Coherence Cache Events Processing
(Doc ID 2542646.1)
Last updated on NOVEMBER 19, 2020
Applies to:Oracle Coherence - Version 126.96.36.199.0 and later
Information in this document applies to any platform.
A customer reported that in coherence 12.2.1.x.x version, persistence snapshot would suspend operations on a distributed cache services then resume operations once the snapshot is completed.
1. If a client keeps executing puts/gets on caches of a distributed service when a snapshot is triggered, will cache events be queued and played after the service resumes? Alternatively, will cache events be lost? Alternatively, will the client's puts/gets fail with a timeout?
2. If there are queued events (event backlog), and have interceptors listening to these events and calling entry processors, will they (even interceptor and entry processors) be allowed to complete before the snapshot operation starts? Will they immediately interrupted? Will they resume once the snapshot is done?
3. How will snapshot impact 24/7 database replication to the HotCache enabled Coherence clusters.
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