diff options
| author | Krishnan Parthasarathi <kp@gluster.com> | 2011-09-21 11:53:45 +0530 |
|---|---|---|
| committer | Vijay Bellur <vijay@gluster.com> | 2011-09-23 06:11:32 -0700 |
| commit | 1fdcbb61872b0a849490d1f0de4fdb545e2865aa (patch) | |
| tree | 97c9fa63e621594bbd101d5715189435a65c713e /xlators/mgmt/glusterd/src/glusterd-volgen.c | |
| parent | 95876fa0ee03b0ee4cd31fa9874b4de596ae70a4 (diff) | |
rpc: No timeouts for lock fops.
As of today, all fops bail out after 30 mins by default. This is not desirable
with lock fops since it could be 'rightfully blocked' for a really long time.
But the client would assume that the lock fop has 'expired' after 30 mins and
clean up its references to the locks. Later when the locks xlator decides to
grant it, we are left with an orphan (stale) lock .
This fix exempts lock fops from timeouts. Only on network disruptions both
client and server decide to 'clean up' the locks held.
Change-Id: If1d74ba21113650b976728e9b764c551a0a49e59
BUG: 3617
Reviewed-on: http://review.gluster.com/478
Tested-by: Gluster Build System <jenkins@build.gluster.com>
Reviewed-by: Amar Tumballi <amar@gluster.com>
Diffstat (limited to 'xlators/mgmt/glusterd/src/glusterd-volgen.c')
0 files changed, 0 insertions, 0 deletions