# Restarting Logstash vs Manual Stopping & Starting

**URL:** <https://discuss.elastic.co/t/restarting-logstash-vs-manual-stopping-starting/60017>\
**Category:** Logstash\
**Created:** [September 7, 2016, 9:02pm UTC](https://discuss.elastic.co/t/restarting-logstash-vs-manual-stopping-starting/60017 "2016-09-07T21:02:21Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![seth.yes](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/seth.yes/32/11788_2.png) [@seth.yes](https://discuss.elastic.co/u/seth.yes)\
**Post date:** [September 7, 2016, 9:02pm UTC](https://discuss.elastic.co/t/restarting-logstash-vs-manual-stopping-starting/60017/1 "2016-09-07T21:02:21Z")

</div>

I'm doing constant testing on a rather-large filter set in Logstash (~1800 lines).

Restarting Logstash takes 3-5 minutes every time, which really slows down my testing efficiency. I'm considering simply running the consecutive commands:  
'service logstash stop'  
'service logstash start'

Is there anything I should be concerned about by restarting Logstash this way? It is definitely a much faster way to develop on Logstash. I know this bypasses the configtest, but that's not really of a concern to me, as the plugin I'm currently debugging doesn't get checked by the configtest very in-depth anyways.

---

<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:** [July 6, 2017, 4:39am UTC](https://discuss.elastic.co/t/restarting-logstash-vs-manual-stopping-starting/60017/2 "2017-07-06T04:39:26Z")

</div>

Closed on July 6, 2017, 4:39am UTC