Page MenuHomePhabricator

Figure out a way to not have the /tmp folder filled
Closed, ResolvedPublic

Description

For some reason jetty is leaving folders of static files for the Blazegraph workbench filled with jars and content that eventually will cause disk-space to run out.

  • Maybe we can force jetty to reuse the old content instead of recreating it at every start.
  • Maybe the docker-compose setting restart will force a clean of /tmp
  • Maybe we can configure /tmp cleaning to happen more frequently
  • Maybe #wikimedia-discovery has a solution already

related things:
https://community.axway.com/s/question/0D52X00007oj1cb/i-have-a-lot-jettydir-files-in-my-tmp-directory-can-i-delete-those
https://askubuntu.com/questions/20783/how-is-the-tmp-directory-cleaned-up#:~:text=The%20cleaning%20of%20%2Ftmp%20is,that%20means%20at%20every%20boot
https://stackoverflow.com/questions/42816048/docker-temporary-files-strategy/55104489

Event Timeline

This also happens on the local vagrant vm so trying things out there seems possible.

Change 620055 had a related patch set uploaded (by Silvan Heintze; owner: Silvan Heintze):
[mediawiki/extensions/Wikibase@master] FP: Use tmpfs for test system's WDQS /tmp folder

https://gerrit.wikimedia.org/r/620055

Change 620055 merged by jenkins-bot:
[mediawiki/extensions/Wikibase@master] FP: Use tmpfs for test system's WDQS /tmp folder

https://gerrit.wikimedia.org/r/620055

Change 666716 had a related patch set uploaded (by Hoo man; owner: Addshore):
[mediawiki/extensions/Wikibase@REL1_35] Backport five FP changes

https://gerrit.wikimedia.org/r/666716

Change 666716 merged by jenkins-bot:
[mediawiki/extensions/Wikibase@REL1_35] Backport five FP changes

https://gerrit.wikimedia.org/r/666716