[Gluster-users] Strange - Missing hostname-trigger_ip-1 resources
ML Wong
wongmlb at gmail.com
Fri Feb 3 02:22:46 UTC 2017
Hello All,
Any pointers will be very-much appreciated. Thanks in advance!
Environment:
Running centOS 7.2.511
Gluster: 3.7.16, with nfs-ganesha on 2.3.0.1 from centos-gluster37 repo
sha1: cab5df4064e3a31d1d92786d91bd41d91517fba8 ganesha-ha.sh
we have used this set up in 3 different gluster, nfs-ganesha environment.
The cluster got setup when we do 'gluster nfs-ganesha enable' , and we can
serve NFS without issues. And i see all the resources got created, but not
the *hostname*-trigger_ip-1 resources? Is that normal?
without *hostname*-trigger_ip-1, according to ganesha-ha.sh, wouldn't it
affect the NFS going into grace, and help to transition the NFS service to
other member nodes at the times of node-failures? please correct me if i
misunderstood.
I tried issuing both 'gluster nfs-ganesha enable', and 'bash -x
/usr/libexec/ganesha/ganesha-ha.sh --setup'. In both scenarios, i still
don't see the *hostname*-trigger_ip-1 got created.
below is my ganesha-ha.conf
HA_NAME="ganesha-ha-01"
HA_VOL_SERVER="vm-fusion1"
HA_CLUSTER_NODES="vm-fusion1,vm-fusion3"
VIP_vm-fusion1="192.168.30.211"
VIP_vm-fusion3="192.168.30.213"
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gluster.org/pipermail/gluster-users/attachments/20170202/8a721454/attachment.html>
More information about the Gluster-users
mailing list