Coherence Federation Active-Active Model Failing With Participant Disconnect From Federation Intermittently
(Doc ID 2205686.1)
Last updated on JUNE 12, 2018
Applies to:Oracle Coherence - Version 18.104.22.168.0 and later
Information in this document applies to any platform.
The customer was running two local clusters in a federated model to support an active-active configuration. When sending read and writes to both local clusters in the federation, the customer was seeing one of them stopped to response and then dropped out of the cluster intermittently.
Local clusters are NewYork and Boston.
1. The customer was sending read and write traffic to both local clusters (NewYork#1,NewYork#2, Boston#1,Boston#2), alternating writes and reads between them, e.g., writing to NewYork and reading from Boston, then writing to Boston and reading from New York, and repeating this over and over. The test ran for nearly two hours without any issues and then it failed with Boston dropping out of the federation.
2. Which node on the Boston side stopped responding (Boston#1, Boston#2 or both)? It seemed like in this particular case Boston#1 stopped responding first, then the other Boston#2 nodes stopped responding too.
3. When Boston got dropped from the federation what specifically got dropped (Boston #1, Boston #2 or both)? Only Boston#1 was dropped out of the federation. For this test Customer only had Boston#1 in the list of federated servers (Customer left Boston #2 out of the list).
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