Coherence Member is Getting Stopped in the Cluster with Stuck Threads on .partitionedService.PartitionedCache.ensureIndexReady
(Doc ID 2281566.1)
Last updated on MAY 13, 2022
Applies to:Oracle Coherence - Version 18.104.22.168.0 and later
Information in this document applies to any platform.
After migrating to new Coherence version 22.214.171.124.0, intermittently, the customer is observing deadlock in partitioned cache service worker. Deadlock is "resolved" by the service guardian, which kills staled service. But after the service is killed, the node remains to stay in a cluster, but is useless (as the corresponding service remains dead). The customer used several previous Coherence versions with exactly the same cluster configuration, load profile and data, but didn't see this issue before.
The below given is the log excerpt when member left the cluster with partitioned cache service got stuck on PartitionedCache.ensureIndexReady() call.
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