Attention is currently required from: Malahal.

skmprabhu2@gmail.com would like Malahal to review this change.

View Change

Retry communication with NSM service

We have seen incidents where Ganesha couldn't communicate to rpc.statd.
It uses the same socket over and over resulting into the same TIMEOUT
error every time.

Destroy the nsm client on a failure and recreate it to avoid this
persistent error. This also helps when rpc.statd service gets restarted
for any reason.

Change-Id: Ia9ef2b5a8c82b79efe2f57b755d0e25adb46b26a
Signed-off-by: Malahal Naineni <malahal@us.ibm.com>
(cherry picked from commit 7b1d58899bc13c1f02b6ea1e4849a37e884d212c)
(cherry picked from commit a77f95b7ac21862cffad6e8cbb979562c73baa57)
---
M src/Protocols/NLM/nsm.c
1 file changed, 55 insertions(+), 9 deletions(-)

git pull ssh://review.gerrithub.io:29418/ffilz/nfs-ganesha refs/changes/24/546024/1

To view, visit change 546024. To unsubscribe, or for help writing mail filters, visit settings.