My Oracle Support Banner

Coherence Witness Protocol Wrongly Calculating and Removing Cache Node Rather Proxy Node from the Cluster (Doc ID 2344775.1)

Last updated on APRIL 28, 2020

Applies to:

Oracle Coherence - Version 12.2.1.0.0 to 12.2.1.3.0 [Release 12c]
Information in this document applies to any platform.

Symptoms


In a coherence cluster, multiple storage nodes lost in production failing to communicate with proxy server. User lost multiple cache nodes at the same time in Production. The log data indicates the cache nodes were kicked out of the cluster for failing to communicate with a Proxy node. The proxy node appeared to be running out of memory and doing GC at that time. User expects the proxy to be removed from the cluster to protect the cache nodes whereas it has removed storage nodes. This is a major risk to production because removing the cache nodes causes data loss and based on the scenario it is expected and proxy server to be chosen and removed from the cluster.

 

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
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.