diff options
author | Niels de Vos <ndevos@redhat.com> | 2017-06-21 16:25:33 +0200 |
---|---|---|
committer | Niels de Vos <ndevos@redhat.com> | 2017-07-09 09:12:58 +0000 |
commit | fafe1491ead527ba1024c521013aa90d2ee2b355 (patch) | |
tree | a4237d7f2e08b27391badaa0db6e18c420791519 /events/eventskeygen.py | |
parent | 26241777bf59c7d64c582ce09e557bc2dc97dabb (diff) |
nfs/nlm: handle reconnect for non-NLM4_LOCK requests
When a reply on an NLM-procedure gets stuck, the NFS-client will resend
the request. This can happen through a re-connect in case the connection
was terminated (long delay in the reply on the initial request). Once
that happens, not all NLM-procedures are handled correctly.
Testing this is difficult and time-consuming. There still may be
problems with certain operations, but this definitely makes it behave
much better than before.
The problem occured due to a problem in EC, change-id I18a782903ba
addressed the root cause.
Change-Id: I23b385568e27232951fa3fbd7198a0e5d775a8c2
BUG: 1467313
Signed-off-by: Niels de Vos <ndevos@redhat.com>
Reviewed-on: https://review.gluster.org/17698
Smoke: Gluster Build System <jenkins@build.gluster.org>
CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
Diffstat (limited to 'events/eventskeygen.py')
0 files changed, 0 insertions, 0 deletions