NFS clients can't connect to clustered NFS server after IPaddr2 resource fails over in a Pacemaker cluster
Issue
- The virtual IP address failed over in an active/passive NFS cluster and now the clients can't connect.
- There is a delay of several minutes for clients to reconnect to the clustered NFS server after failover.
Environment
- Red Hat Enterprise Linux 6, 7, or 8 (with the High Availability Add-on)
- Pacemaker
- An active/passive NFS cluster
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.