# Issue with logstash persistence queue for multiple pipelines

**URL:** <https://discuss.elastic.co/t/issue-with-logstash-persistence-queue-for-multiple-pipelines/116446>\
**Category:** Logstash\
**Created:** [January 22, 2018, 8:54am UTC](https://discuss.elastic.co/t/issue-with-logstash-persistence-queue-for-multiple-pipelines/116446 "2018-01-22T08:54:40Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Hemanth\_Gowda](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/hemanth_gowda/32/23886_2.png) [@Hemanth\_Gowda](https://discuss.elastic.co/u/Hemanth_Gowda)\
**Post date:** [January 22, 2018, 8:54am UTC](https://discuss.elastic.co/t/issue-with-logstash-persistence-queue-for-multiple-pipelines/116446/1 "2018-01-22T08:54:40Z")

</div>

Hi Team,  
I have 2 configuration files  
/conf/test.config,  
/conf/test1.config

When i run my logstash instance with first configuration the queue is getting created and i don't want the queue data to be utilized by any other [pipeline.In](http://pipeline.In) my case when i run logstash with test1.config the queue data created by test.config is [utilized.Is](http://utilized.Is) there any way i can lock my queue for specific [instance.By](http://instance.By) the way i am using logstash 5.6.

Regards,  
Hemanth K

---

<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:** [February 19, 2018, 8:54am UTC](https://discuss.elastic.co/t/issue-with-logstash-persistence-queue-for-multiple-pipelines/116446/2 "2018-02-19T08:54:52Z")

</div>

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