Merge ~cjwatson/launchpad-mojo-specs:git-hard-mount into launchpad-mojo-specs:master
Status: | Merged |
---|---|
Merged at revision: | 571f506e0f30432d44b7f294c8534fc6feb113d5 |
Proposed branch: | ~cjwatson/launchpad-mojo-specs:git-hard-mount |
Merge into: | launchpad-mojo-specs:master |
Diff against target: |
13 lines (+1/-1) 1 file modified
mojo-lp-git/services (+1/-1) |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Ioana Lasc (community) | Approve | ||
Review via email: mp+402657@code.launchpad.net |
Commit message
git: Use "hard" NFS client recovery
Description of the change
From nfs(5):
soft / hard Determines the recovery behavior of the NFS client after
an NFS request times out. If neither option is
is specified, then the NFS client fails an NFS request
the NFS client to return an error to the calling
NB: A so-called "soft" timeout can cause silent data
the value of the retrans option may mitigate some of the
I think I initially went for "soft" because retrying forever rather than failing seemed undesirable, and because the code writing to this NFS mount is very limited and known to have reasonable error handling. However, it seems that under load this can also cause the client to
consider the NFS mount dead after relatively short periods of unresponsiveness when it might otherwise be able to recover. Let's see if using the default of "hard" works more gracefully in practice.