You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Hyukjin Kwon (JIRA)" <ji...@apache.org> on 2019/05/21 04:35:40 UTC
[jira] [Resolved] (SPARK-12430) Temporary folders do not get
deleted after Task completes causing problems with disk space.
[ https://issues.apache.org/jira/browse/SPARK-12430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hyukjin Kwon resolved SPARK-12430.
----------------------------------
Resolution: Incomplete
> Temporary folders do not get deleted after Task completes causing problems with disk space.
> -------------------------------------------------------------------------------------------
>
> Key: SPARK-12430
> URL: https://issues.apache.org/jira/browse/SPARK-12430
> Project: Spark
> Issue Type: Bug
> Components: Spark Core
> Affects Versions: 1.5.1, 1.5.2, 1.6.0
> Environment: Ubuntu server
> Reporter: Fede Bar
> Priority: Major
> Labels: bulk-closed
>
> We are experiencing an issue with automatic /tmp folder deletion after framework completes. Completing a M/R job using Spark 1.5.2 (same behavior as Spark 1.5.1) over Mesos will not delete some temporary folders causing free disk space on server to exhaust.
> Behavior of M/R job using Spark 1.4.1 over Mesos cluster:
> - Launched using spark-submit on one cluster node.
> - Following folders are created: */tmp/mesos/slaves/id#* , */tmp/spark-#/* , */tmp/spark-#/blockmgr-#*
> - When task is completed */tmp/spark-#/* gets deleted along with */tmp/spark-#/blockmgr-#* sub-folder.
> Behavior of M/R job using Spark 1.5.2 over Mesos cluster (same identical job):
> - Launched using spark-submit on one cluster node.
> - Following folders are created: */tmp/mesos/mesos/slaves/id** * , */tmp/spark-***/ * ,{color:red} /tmp/blockmgr-***{color}
> - When task is completed */tmp/spark-***/ * gets deleted but NOT shuffle container folder {color:red} /tmp/blockmgr-***{color}
> Unfortunately, {color:red} /tmp/blockmgr-***{color} can account for several GB depending on the job that ran. Over time this causes disk space to become full with consequences that we all know.
> Running a shell script would probably work but it is difficult to identify folders in use by a running M/R or stale folders. I did notice similar issues opened by other users marked as "resolved", but none seems to exactly match the above behavior.
> I really hope someone has insights on how to fix it.
> Thank you very much!
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org