# Logstash on Kubernetes pipeline terminated if resources.limits.cpu/memory is set

**URL:** <https://discuss.elastic.co/t/logstash-on-kubernetes-pipeline-terminated-if-resources-limits-cpu-memory-is-set/220026>\
**Category:** Logstash\
**Created:** [February 19, 2020, 4:24pm UTC](https://discuss.elastic.co/t/logstash-on-kubernetes-pipeline-terminated-if-resources-limits-cpu-memory-is-set/220026 "2020-02-19T16:24:53Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![danksim](https://avatars.discourse-cdn.com/v4/letter/d/a88e57/32.png) [@danksim](https://discuss.elastic.co/u/danksim)\
**Post date:** [February 19, 2020, 4:24pm UTC](https://discuss.elastic.co/t/logstash-on-kubernetes-pipeline-terminated-if-resources-limits-cpu-memory-is-set/220026/1 "2020-02-19T16:24:53Z")

</div>

When running Logstash (as a statefulset) on EKS with `resources.limits.cpu/memory` set, the pods tend to exit with the `pipeline terminated` message resulting in `CrashLoopBackoff`s. The input is a kafka stream. When I do a `kubectl edit` and delete the `limits` part of the manifest, it starts to work fine again. The request and the limits were matching at `cpu: "1"` and `memory: 512Mi`. Not sure what the `limits` field has to do with this. Any idea?

---

<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:** [March 18, 2020, 4:25pm UTC](https://discuss.elastic.co/t/logstash-on-kubernetes-pipeline-terminated-if-resources-limits-cpu-memory-is-set/220026/2 "2020-03-18T16:25:04Z")

</div>

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