Is not needed, and causes proxying to fail during NFS outages.
Description
Description
Details
Details
| Project | Branch | Lines +/- | Subject | |
|---|---|---|---|---|
| operations/puppet | production | +0 -3 | labstore: Disable some NFS mounts on project-proxy |
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | yuvipanda | T105720 Labs team reliability goal for Q1 2015/16 | |||
| Resolved | Andrew | T102240 Audit projects' use of NFS, and remove it where not necessary | |||
| Declined | None | T102369 Remove NFS completely from project-proxy project |
Event Timeline
Comment Actions
Change 242437 had a related patch set uploaded (by Yuvipanda):
labstore: Disable some NFS mounts on project-proxy
Comment Actions
Change 242437 merged by Yuvipanda:
labstore: Disable some NFS mounts on project-proxy
Comment Actions
I do not think that removing the backup process from the project-proxy servers is a beneficial thing. The NFS seems perfectly OK to have on there as long as it isn't running critical processes or mounted on /home.
If NFS was badly down, and we wanted to save the other things, the cron could be commented out, and the NFS unmounted until the outage was over.
Comment Actions
Mentioned in SAL (#wikimedia-cloud) [2020-06-16T21:33:04Z] <bstorm_> setting "profile::wmcs::nfsclient::mode: soft" on the project T102369 T127559