Experienced Lost Partitions When Data Pods Restarted In a Coherence cluster in Kubernetes using the Coherence operator.
(Doc ID 2699538.1)
Last updated on DECEMBER 13, 2022
Applies to:Oracle Coherence - Version 18.104.22.168.0 and later
Information in this document applies to any platform.
A Customer has experienced losing partitions when data pods restarted in Kubernetes. They were running a Coherence cluster in Kubernetes using the Coherence operator. They experienced several partitions lost events when the pods were restarted, either unexpectedly or via a planned K8S Node drain/restart operation. They had configured a backup count of 1, this was unexpected.
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