>
> That is why we have the release_IP dBus command, it signals the Ganesha that
> is giving up clients to drop their locks.
Thanks a lot Frank. Right now in our HA solution, we do not send any
event. So by default I guess it takes "EVENT_TAKE_IP". Will try out
"EVENT_RELEASE_IP".
So IIUC, the only difference between "EVENT_TAKE_IP" and
"EVENT_RELEASEIP" is that TAKE_IP just loads nfsv4 clients in memory to
validate them during recovery where as release IP shall expire all the
existing clients of that IP (which involves releasing open and lock
state) and then loads them in memory for recovery validation?
And what about NLM locks?
<code-snippet>
else {
nfs_release_nlm_state(gsp->ipaddr);
if (gsp->event == EVENT_RELEASE_IP)
nfs_release_v4_client(gsp->ipaddr);
else
nfs4_load_recov_clids_nolock(gsp);
}
<<<<<
"nfs_release_nlm_state" seems to be notifying the NLM clients but I do
not see any calls to flush the granted locks at the back-end as well?
Thanks,
Soumya
>
> Frank
>
>
> ---
> This email has been checked for viruses by Avast antivirus software.
> https://www.avast.com/antivirus
>
------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity planning
reports.http://sdm.link/zohodev2dev
_______________________________________________
Nfs-ganesha-devel mailing list
Nfs-ganesha-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel
