Is Coherence Cluster Allows to Set the IPMonitor Timeout Value Differently for the Members?
(Doc ID 2953910.1)
Last updated on AUGUST 24, 2023
Applies to:Oracle Coherence - Version 126.96.36.199.0 and later
Information in this document applies to any platform.
Coherence customers are using the stretch cluster across the subnets/DCs. In some cases, they need different IPMonitor timeouts (TCP ring Health). Even with better understanding of the member eviction explanation with respect to witness protocol, customers want to try different settings per subnet/logical group of nodes of the cluster. Is this allowed as per the Coherence core runtime? Would this be OK or else would it create other repercussions? User tested with 14cFP (188.8.131.526) not seen any issue in cluster forming:
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