# Dedicated private temporary directory cleanup policy

**URL:** <https://discuss.elastic.co/t/dedicated-private-temporary-directory-cleanup-policy/207720>\
**Category:** Elasticsearch\
**Created:** [November 13, 2019, 2:21pm UTC](https://discuss.elastic.co/t/dedicated-private-temporary-directory-cleanup-policy/207720 "2019-11-13T14:21:01Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![imrimt](https://avatars.discourse-cdn.com/v4/letter/i/76d3ee/32.png) [@imrimt](https://discuss.elastic.co/u/imrimt)\
**Post date:** [November 13, 2019, 2:21pm UTC](https://discuss.elastic.co/t/dedicated-private-temporary-directory-cleanup-policy/207720/1 "2019-11-13T14:21:02Z")

</div>

As per this documentation: [https://www.elastic.co/guide/en/elasticsearch/reference/6.8/es-tmpdir.html](https://www.elastic.co/guide/en/elasticsearch/reference/6.8/es-tmpdir.html), we should configure a dedicated temp directory when running Elasticsearch on Linux using the tar.gz distribution so that the private temp directory is not subject to system's automatic cleanup. In that case, do we have to do the cleaning up ourselves? Or will Elasticsearch handle this upon startup?

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [December 11, 2019, 2:21pm UTC](https://discuss.elastic.co/t/dedicated-private-temporary-directory-cleanup-policy/207720/2 "2019-12-11T14:21:08Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.