path: root/tests/basic/afr/heal-quota.t
diff options
authorKaleb S KEITHLEY <>2016-05-23 15:41:51 -0400
committerKaleb KEITHLEY <>2016-05-24 02:36:44 -0700
commit2de43f41b0d9a4e6b08447e86cc83ac3f4bc7684 (patch)
tree3db5cba7d7a3cab7a142981d52670ac20f14c2bd /tests/basic/afr/heal-quota.t
parentdf931b2c6b2755e57b9d49e3fb045646e6e892fd (diff)
common-ha: post fail-back, ganesha.nfsds are not put into NFS-GRACE
A little known, rarely used feature of pacemaker called "notification" is used to follow the status of the ganesha.nfsds in the cluster. This is done with location constraints and other Black Magick. When a nfsd dies, the ganesha-active attribute is cleared, the associated floating IP (VIP) fails over to another node, and the ganesha_grace notify method is invoked with post-stop on all the nodes where the ganesha.nfsd is still running. The notify methods send dbus msgs to put their nfsds into NFS-GRACE, and the nfsds perform their grace processing, e.g. taking over locks from the failed nfsd. N.B. Fail-back was originally not planned to be a feature for glusterfs-3.7, but we sorta got it for free. For fail-back, the opposite occurs. The ganesha-active attribute is recreated, the floating IP fails back, and the notify method is invoked with pre-start on all the nodes where the surviving ganesha.nfsds continue to run. The notify methods send dbus msgs again to put their nsfds into NFS-GRACE again, and the nfsds clean up their locks. backport mainline > > BUG: 1338967 release-3.8 > > BUG: 1338968 Change-Id: I3fc64afa20ae3a928143d69aa533a8df68dd680e BUG: 1338969 Signed-off-by: Kaleb S KEITHLEY <> Reviewed-on: NetBSD-regression: NetBSD Build System <> Smoke: Gluster Build System <> CentOS-regression: Gluster Build System <> Reviewed-by: soumya k <>
Diffstat (limited to 'tests/basic/afr/heal-quota.t')
0 files changed, 0 insertions, 0 deletions