Cluster Unavailable For a Long Period After a Rolling Restart Test
Last updated on NOVEMBER 03, 2016
Applies to:Oracle Coherence - Version 3.7.1 to 3.7.1 [Release AS10g]
Information in this document applies to any platform.
During a rolling restart test, when the senior node for the DistributedCache service was restarted, the cluster become unresponsive and a large number of UDP messages were observed in tcp dumps. Both the TCP Ring and IpMonitor death detection mechanisms where enabled with their default times. The cluster was available again after 5 minutes, which matches the default timeout for UDP packet delivery to timeout.
What is the root cause and how can we avoid this situation?
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms