# Disk Pressure due to accumulating logs and runtime\_resources

**URL:** <https://discuss.ray.io/t/disk-pressure-due-to-accumulating-logs-and-runtime-resources/11604>\
**Category:** Kubernetes\
**Created:** [July 28, 2023, 3:45pm UTC](https://discuss.ray.io/t/disk-pressure-due-to-accumulating-logs-and-runtime-resources/11604 "2023-07-28T15:45:50Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![koziello](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ray.io/koziello/32/4849_2.png) [@koziello](https://discuss.ray.io/u/koziello)\
**Post date:** [July 28, 2023, 3:45pm UTC](https://discuss.ray.io/t/disk-pressure-due-to-accumulating-logs-and-runtime-resources/11604/1 "2023-07-28T15:45:50Z")

</div>

**How severe does this issue affect your experience of using Ray?**

- Medium: It contributes to significant difficulty to complete my task, but I can work around it.

Hello,  
we’re having a Ray cluster setup in Kubernetes and we noticed disks getting full over time with logs and runtime resources. As a result our head node would flip with disk\_pressure error once it reached 91% of disk utilization. I’ve created a cron task to clear files from /tmp/ray location for previous sessions, preserving only what’s in session\_latest.  
What are the consequences of deleting those files? How can we be sure we won’t disrupt an user by deleting the runtime\_env that he’s using? What is the preffered way to handle this situation?  
Thanks!

Please refer to the screenshot

 ![image](https://us1.discourse-cdn.com/flex020/uploads/ray/original/2X/1/1637aa2da748f439841d9a2d1f8b8b7d1032e987.png)