How Is ZFS-SA Supposed To Be Notified To Release Stored.lck Upon Cluster Failover?
(Doc ID 2194544.1)
Last updated on JULY 12, 2022
Applies to:Oracle Communications Messaging Server - Version 7.0.0 and later
Information in this document applies to any platform.
We are using Veritas Cluster Server (VCS). We had a sever outage on a new MS store backend in the morning, and it was made worse when cluster failover failed because stored.lck was still locked, as described in Doc ID 1596986.1. Of course, because it was under cluster control, the error messages were not easy to find, so it took extra time to find out what the problem was.
The result being that something that was pretty bad to start with, got escalated to even worse because cluster failover also failed, leaving the service down for more than a few minutes.
It was still locked because of the way the first node went down. The NFS server (the ZFS-SA) was not notified.
Question: Is there some other way that the ZFS-SA NFS setup allows SunCluster to notify the NFS server that the other node has failed and the locks should be released?
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