Why does active TIBCO node fails to identify a network failure and is successful to obtain a lock on NFS4 server even when the lock is with standby node?
Issue
- When the active
TIBCOnode loses network connectivity, the standby node obtains the lock to the files on shared storage and becomes the active node. - The previous active node does not detect it has lost connectivity the other node and shared storage. It does not go into standby mode.
- When the previous active node regains network connectivity, it still believes it is the active node. It does not try to regain the lock to the files on shared storage and thus still does not go into standby.
- If this sequence of events occurs, TIBCO will be in a dual-active EMS scenario, which is not expected, and file corruption can occur.
Environment
- Red Hat Enterprise Linux 5, 6 (NFS4 client)
- TIBCO EMS (uses flock / fcntl locks to protect writes to files)
- NFSv4
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.
Close
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.