# How to check old pipeline is terminated or not in logstash during config reload

**URL:** <https://discuss.elastic.co/t/how-to-check-old-pipeline-is-terminated-or-not-in-logstash-during-config-reload/318514>\
**Category:** Logstash\
**Created:** [November 9, 2022, 7:25am UTC](https://discuss.elastic.co/t/how-to-check-old-pipeline-is-terminated-or-not-in-logstash-during-config-reload/318514 "2022-11-09T07:25:14Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![teja\_tata](https://avatars.discourse-cdn.com/v4/letter/t/dec6dc/32.png) [@teja\_tata](https://discuss.elastic.co/u/teja_tata)\
**Post date:** [November 9, 2022, 7:25am UTC](https://discuss.elastic.co/t/how-to-check-old-pipeline-is-terminated-or-not-in-logstash-during-config-reload/318514/1 "2022-11-09T07:25:14Z")

</div>

> **[Reloading the Config File | Logstash Reference \[7.17\] | Elastic](https://www.elastic.co/guide/en/logstash/7.17/reloading-config.html#_how_automatic_config_reloading_works)**

From the above documentation we could see that _Logstash swaps the existing pipeline with the new pipeline. If the checks fail, the old pipeline continues to function, and the errors are propagated to the console._  
**How could we know whether the existing pipeline is terminated after new pipeline is created. And a general doubt how much memory does a pipeline take after it is created ?**

---

<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:** [December 7, 2022, 7:25am UTC](https://discuss.elastic.co/t/how-to-check-old-pipeline-is-terminated-or-not-in-logstash-during-config-reload/318514/2 "2022-12-07T07:25:53Z")

</div>

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