# Pipelines.yml and best practices using this approach (+auto config reload)
**URL:** https://discuss.elastic.co/t/pipelines-yml-and-best-practices-using-this-approach-auto-config-reload/175824
**Category:** Logstash
**Created:** [April 8, 2019, 11:33am UTC](https://discuss.elastic.co/t/pipelines-yml-and-best-practices-using-this-approach-auto-config-reload/175824 "2019-04-08T11:33:47Z")
**Posts on this page:** 6
**Page:** 1
### Author:  [@saif3r](https://discuss.elastic.co/u/saif3r)
#### Post date: [April 8, 2019, 11:33am UTC](https://discuss.elastic.co/t/pipelines-yml-and-best-practices-using-this-approach-auto-config-reload/175824/1 "2019-04-08T11:33:47Z")
Hello Guys,
I just created several different pipelines and I'm running them using pipelines.yml and systemctl command to control logstash service. I have a few questions regarding this approach, I hope you can answer them:
1. systemctl stop logstash.service stops all pipelines defined in the pipielines.yml. Is it possible to stop single pipeline using this approach?
2. Is it possible to automaticaly relog a config of one particular pipeline (similar to config.reload.automatic)?
3. What is the best practice for an architecture focused around different pipelines? I plan to have a few jdbc and flat files pipelines and I'm looking for best approach to do so. As for now, using pipelines.yml seems to be an obvious choice.
Thanks in advance.
---
### Author:  [@Badger](https://discuss.elastic.co/u/Badger)
#### Post date: [April 8, 2019, 12:08pm UTC](https://discuss.elastic.co/t/pipelines-yml-and-best-practices-using-this-approach-auto-config-reload/175824/2 "2019-04-08T12:08:47Z")
For 2 ... yes, if you enable -r then if you update the configuration of a single pipeline it will get reloaded.
---
### Author:  [@saif3r](https://discuss.elastic.co/u/saif3r)
#### Post date: [April 9, 2019, 12:46pm UTC](https://discuss.elastic.co/t/pipelines-yml-and-best-practices-using-this-approach-auto-config-reload/175824/3 "2019-04-09T12:46:31Z")
I launched logstash service using below command
> sudo systemctl start logstash.service -r
and it seems like my configuration changes have no effect. The pipieline continues to work with initial settings.
---
### Author:  [@Badger](https://discuss.elastic.co/u/Badger)
#### Post date: [April 9, 2019, 12:55pm UTC](https://discuss.elastic.co/t/pipelines-yml-and-best-practices-using-this-approach-auto-config-reload/175824/4 "2019-04-09T12:55:47Z")
Run
```
sudo systemctl show logstash
```
It should include a line like
```
FragmentPath=/etc/systemd/system/logstash.service
```
Edit that file and change the ExecStart line to include -r.
---
### Author:  [@saif3r](https://discuss.elastic.co/u/saif3r)
#### Post date: [April 9, 2019, 1:32pm UTC](https://discuss.elastic.co/t/pipelines-yml-and-best-practices-using-this-approach-auto-config-reload/175824/5 "2019-04-09T13:32:46Z")
This is great, thank you!
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [May 7, 2019, 1:32pm UTC](https://discuss.elastic.co/t/pipelines-yml-and-best-practices-using-this-approach-auto-config-reload/175824/6 "2019-05-07T13:32:51Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.