<div dir="ltr">Thanks so much for your promptly response, Soumya.<div>That helps clearing out one of my questions. I am trying to figure out why NFS service did not failover/pick-up the NFS clients last time when one of our cluster-nodes failed.</div><div><br></div><div>Though i could see, in corosync.log, a notify got sent to the cluster the failed node, the election, and the IP failover process seems to all be finished with in around minute. However, after the IP failover to the destinated node, i tried to do a "showmount -e localhost" - the command got hung. But, i still see ganesha-nfsd is running in the host. To your expertise, if i understand the process correctly, given that i keep all the default timeout/interval settings for nfs-mon, nfs-grace, the entire IP failover, and NFS service failover process should be completed within 2 minutes. Am i correct?</div><div><br></div><div>Your help is again appreciated.</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Feb 2, 2017 at 11:42 PM, Soumya Koduri <span dir="ltr"><<a href="mailto:skoduri@redhat.com" target="_blank">skoduri@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<span class=""><br>
<br>
On 02/03/2017 07:52 AM, ML Wong wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hello All,<br>
Any pointers will be very-much appreciated. Thanks in advance!<br>
<br>
Environment:<br>
Running centOS 7.2.511<br>
Gluster: 3.7.16, with nfs-ganesha on 2.3.0.1 from centos-gluster37 repo<br>
sha1: cab5df4064e3a31d1d92786d91bd41<wbr>d91517fba8 ganesha-ha.sh<br>
<br>
we have used this set up in 3 different gluster, nfs-ganesha<br>
environment. The cluster got setup when we do 'gluster nfs-ganesha<br>
enable' , and we can serve NFS without issues. And i see all the<br>
resources got created, but not the *hostname*-trigger_ip-1 resources? Is<br>
that normal?<br>
<br>
</blockquote>
<br></span>
Yes it is normal. With change [1], new resource agent attributes have been introduced in place of *-trigger_ip-1 to monitor, move the VIP and put the cluster in grace. More details are in the change# commit msg.<br>
<br>
Thanks,<br>
Soumya<br>
<br>
[1] <a href="https://github.com/gluster/glusterfs/commit/e8121c4afb3680f532b450872b5a3ffcb3766a97" rel="noreferrer" target="_blank">https://github.com/gluster/glu<wbr>sterfs/commit/e8121c4afb3680f5<wbr>32b450872b5a3ffcb3766a97</a><br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">
without *hostname*-trigger_ip-1, according to ganesha-ha.sh, wouldn't it<br>
affect the NFS going into grace, and help to transition the NFS service<br>
to other member nodes at the times of node-failures? please correct me<br>
if i misunderstood.<br>
<br>
I tried issuing both 'gluster nfs-ganesha enable', and 'bash -x<br>
/usr/libexec/ganesha/ganesha-h<wbr>a.sh --setup'. In both scenarios, i still<br>
don't see the *hostname*-trigger_ip-1 got created.<br>
<br>
below is my ganesha-ha.conf<br>
HA_NAME="ganesha-ha-01"<br>
HA_VOL_SERVER="vm-fusion1"<br>
HA_CLUSTER_NODES="vm-fusion1,v<wbr>m-fusion3"<br>
VIP_vm-fusion1="192.168.30.211<wbr>"<br>
VIP_vm-fusion3="192.168.30.213<wbr>"<br>
<br>
<br>
<br>
<br></span>
______________________________<wbr>_________________<br>
Gluster-users mailing list<br>
<a href="mailto:Gluster-users@gluster.org" target="_blank">Gluster-users@gluster.org</a><br>
<a href="http://lists.gluster.org/mailman/listinfo/gluster-users" rel="noreferrer" target="_blank">http://lists.gluster.org/mailm<wbr>an/listinfo/gluster-users</a><br>
<br>
</blockquote>
</blockquote></div><br></div>