# Scylla is killed due to space issue

**URL:** https://forum.scylladb.com/t/scylla-is-killed-due-to-space-issue/4564
**Category:** ScyllaDB
**Tags:** error-message, operator, kubernetes
**Created:** [March 4, 2025, 3:08pm UTC](https://forum.scylladb.com/t/scylla-is-killed-due-to-space-issue/4564 "2025-03-04T15:08:56Z")
**Posts on this page:** 1
**Showing post:** 2

<div class="post-metadata">

### Author: ![Yehuda\_Lebi](https://sea2.discourse-cdn.com/flex016/user_avatar/forum.scylladb.com/yehuda_lebi/32/1021_2.png) [@Yehuda\_Lebi](https://forum.scylladb.com/u/Yehuda_Lebi)
#### Post date: [March 31, 2025, 6:46am UTC](https://forum.scylladb.com/t/scylla-is-killed-due-to-space-issue/4564/2 "2025-03-31T06:46:35Z")

</div>

Your ScyllaDB pods are being evicted because they are exceeding the ephemeral storage allocation you’ve set (256MB).

The logs clearly state:

```auto
The node was low on resource: ephemeral-storage.

```

256MB ephemeral storage is extremely limited for running ScyllaDB, even for just logs and basic container overhead.

You have two practical solutions here:

1. Increase ephemeral storage requests and limits  
In your Helm values file (`values.yaml`), increase ephemeral storage requests and limits, for example:

```auto
resources:
  requests:
    ephemeral-storage: "2Gi"
  limits:
    ephemeral-storage: "4Gi"

```

Adjust based on your environment, number of nodes, and expected log verbosity.

1. Use Persistent Storage for Logs

---

_[View the full topic](https://forum.scylladb.com/t/scylla-is-killed-due-to-space-issue/4564)._