As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.
Hello I'm having trouble finding out what files can be erasen from the /tmp folder.
Recently we assigned a 1tb storage to Alfresco server and around 900gb of space is taken by the /tmpfolder. Any advice on how to handle this issue?
Good morning.
Could you please be more concrete, please? Which files are "huges"?
Cheers.
Good Morning, yes of course. I'm seeing this huge space being taken in the tmp folder of around 900GB. Just wondering if there is an advice on how to deal with this, like generating a task that erases de tmp content or some configuration to be made.
I'm attaching the extract where it says the tmp folder takes up to 908gb.
Thanks in advance
System information as of Fri Aug 27 20:05:52 UTC 2021
System load: 0.32 Processes: 169Usage of /: 95.9% of 968.92GB Users logged in: 0Memory usage: 29% IPv4 address for ens33: 172.26.102.104Swap usage: 19%
=> / is using 95.9% of 968.92GB
root@:/home/alfresco# du /tmp -l -h | sort -h4.0K /tmp/.ICE-unix4.0K /tmp/.Test-unix4.0K /tmp/.X11-unix4.0K /tmp/.XIM-unix4.0K /tmp/.font-unix4.0K /tmp/jetty-0.0.0.0-8983-webapp-_solr-any-1006956459560672389.dir....4.0K /tmp/jetty-0.0.0.0-8983-webapp-_solr-any-943457194554236406.dir4.0K /tmp/jetty-0.0.0.0-8983-webapp-_solr-any-956985747459471869.dir4.0K /tmp/jetty-0.0.0.0-8983-webapp-_solr-any-992095262186214672.dir4.0K /tmp/jetty-0.0.0.0-8983-webapp-_solr-any-993116675881171733.dir4.0K /tmp/jetty-0.0.0.0-8983-webapp-_solr-any-993491343541809381.dir4.0K /tmp/jetty-0.0.0.0-8983-webapp-_solr-any-994125659065502289.dir4.0K /tmp/jetty-0.0.0.0-8983-webapp-_solr-any-997338741930792060.dir4.0K /tmp/lu1405t1ayyd.tmp4.0K /tmp/snap.lxd/tmp4.0K /tmp/systemd-private-cff0ed14cbfa4b80b31056adad4678e7-systemd-logind.service-L2Hojg/tmp4.0K /tmp/systemd-private-cff0ed14cbfa4b80b31056adad4678e7-systemd-resolved.service-3ZCXli/tmp4.0K /tmp/systemd-private-cff0ed14cbfa4b80b31056adad4678e7-systemd-timesyncd.service-7dSkif/tmp4.0K /tmp/vmware-root_630-26886196968.0K /tmp/snap.lxd8.0K /tmp/systemd-private-cff0ed14cbfa4b80b31056adad4678e7-systemd-logind.service-L2Hojg8.0K /tmp/systemd-private-cff0ed14cbfa4b80b31056adad4678e7-systemd-resolved.service-3ZCXli8.0K /tmp/systemd-private-cff0ed14cbfa4b80b31056adad4678e7-systemd-timesyncd.service-7dSkif68K /tmp/hsperfdata_alfresco908G /tmp
You didn't answer my question: I'd like to know which files are huge inside of temp folder in order to reply you properly. You just have paste a resume list with 8Kb per document... that it not helping at all
But, following my experience maybe the huge file that you have are the suggester_input/sort files. If this is your case too: the size of the indixes depends on the amount of documents, nodes and relating metadata. If your content is mainly text-based (Office, PDF, HTML...), your indices can be a substantial (and important) part of the storage, compared to the size of the contentstore.
Relating to the WFSIterator* files in /tomcat/temp, it is usual to deactivate SOLR suggester in <solrRootDir>/workspace-SpacesStore/conf/solrcore.properties (solr.suggester.enabled=false) to avoid these huge files in tomcat/temp. Then, you can clean tomcat/temp and restart Alfresco.
In case you disable the suggester: if you launch a query on the UI Solr won't suggest you any similar term. E.g.: if you write "Alfresdo", it won't suggest you "Alfresco".
I hope this information can help you.
Cheers,
Cris.
