# LS constantly reloading failing pipeline & exhausting host connections

**URL:** <https://discuss.elastic.co/t/ls-constantly-reloading-failing-pipeline-exhausting-host-connections/373571>\
**Category:** Logstash\
**Created:** [January 23, 2025, 9:56am UTC](https://discuss.elastic.co/t/ls-constantly-reloading-failing-pipeline-exhausting-host-connections/373571 "2025-01-23T09:56:11Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![jdswifty](https://avatars.discourse-cdn.com/v4/letter/j/779978/32.png) [@jdswifty](https://discuss.elastic.co/u/jdswifty)\
**Post date:** [January 23, 2025, 9:56am UTC](https://discuss.elastic.co/t/ls-constantly-reloading-failing-pipeline-exhausting-host-connections/373571/1 "2025-01-23T09:56:11Z")

</div>

Noticed that when I have a pipeline, with an Elasticsearch output, that is failing, LS is then reloading the pipeline over & over but not clearing down the previously spawned connections to ES so I end up with connection limits being hit .

Using pipeline.yml to load in individual pipeline configs.

Is this a known issue or is there a config entry i can use to stop the connection exhaustion