You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Fede Bar (JIRA)" <ji...@apache.org> on 2015/12/18 21:32:46 UTC

[jira] [Created] (SPARK-12430) Temporary folders do not get deleted after Task completes causing problems with disk space.

Fede Bar created SPARK-12430:
--------------------------------

             Summary: 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: Block Manager, Shuffle, Spark Submit
    Affects Versions: 1.5.2, 1.5.1
         Environment: Ubuntu server
            Reporter: Fede Bar
             Fix For: 1.4.1


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
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org