GitHub user swaroopchenchu closed a discussion: Ephemeral local storage usage 
exceeds the total limit, Apache hop Pod Crashing

We are running Apache Hop 2.7.0, deployed via Helm chart on Google Kubernetes 
Engine (GKE).

To prevent pod eviction (since Apache Hop consumes significant resources during 
pipeline execution), we configured the following resource requests and limits:

limits:
  ephemeral-storage: 70Gi
  memory: 16Gi
requests:
  cpu: 1
  ephemeral-storage: 60Gi
  memory: 8Gi


However, the pod still crashes while the pipeline is running.

📌 Pod Events
Normal   Scheduled      57m   default-scheduler  Successfully assigned 
etl/hop-server-7b88f876c8-ld8bv to gke-exito-lab-1-obp-dabc0b17-8cjc
Normal   Pulling        57m   kubelet            Pulling image 
"us-central1-docker.pkg.dev/product-obp/obp/apache-hop:2.7.0"
Normal   Pulled         56m   kubelet            Successfully pulled image in 
27.7s (image size ~940MB)
Normal   Created        56m   kubelet            Created container: hop
Normal   Started        56m   kubelet            Started container hop
⚠️ Warning Evicted       4m   kubelet            Pod ephemeral local storage 
usage exceeds the total limit of containers (70Gi)
Normal   Killing        4m   kubelet            Stopping container hop
⚠️ Warning FailedKillPod 3m57s kubelet           failed to kill container 
(ttrpc: closed)

🤔 Observation / Question

The eviction reason clearly indicates ephemeral local storage exhaustion

The pipeline performs a large number of database lookups

Question:
Could the high number of database lookups (temporary files, caching, sorting, 
or transform spill-to-disk) be causing excessive ephemeral storage usage, 
leading to pod eviction?

📷 Reference
<img width="803" height="271" alt="Pod eviction event" 
src="https://github.com/user-attachments/assets/f70442e3-668d-45a4-92b9-e0c1efa2f6b4";
 />

Could anyone please guide here.

Thanks

GitHub link: https://github.com/apache/hop/discussions/6429

----
This is an automatically sent email for [email protected].
To unsubscribe, please send an email to: [email protected]

Reply via email to