# Question about shipping instance and indexing instance in scalable deployment of Logstash

**URL:** <https://discuss.elastic.co/t/question-about-shipping-instance-and-indexing-instance-in-scalable-deployment-of-logstash/72552>\
**Category:** Logstash\
**Created:** [January 24, 2017, 2:18am UTC](https://discuss.elastic.co/t/question-about-shipping-instance-and-indexing-instance-in-scalable-deployment-of-logstash/72552 "2017-01-24T02:18:38Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![yuanlinios](https://avatars.discourse-cdn.com/v4/letter/y/db5fbb/32.png) [@yuanlinios](https://discuss.elastic.co/u/yuanlinios)\
**Post date:** [January 24, 2017, 2:18am UTC](https://discuss.elastic.co/t/question-about-shipping-instance-and-indexing-instance-in-scalable-deployment-of-logstash/72552/1 "2017-01-24T02:18:38Z")

</div>

Hello experts

According to the "Deploying and Scaling Logstash" guide, I plan to use following structure for my logstash deployment:

source -\> HA proxy -\> multiple shipping instances [input, MQ output] -\> MQ -\> multiple indexing instances [MQ input, filter, output] -\> ES

As for the shipping instance and indexing instance, should I separate them into different "LS instances"? or just run both in the same "LS instance" (e.g, with 2 configs in /etc/logstash/conf.d/, 1 for shipping and 1 for indexing) ?

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [January 24, 2017, 8:12am UTC](https://discuss.elastic.co/t/question-about-shipping-instance-and-indexing-instance-in-scalable-deployment-of-logstash/72552/2 "2017-01-24T08:12:49Z")

</div>

If you have inputs that do not handle back-pressure well and are looking to have the MQ buffer data in case of issues downstream in order to not lose data, you should use separate Logstash instances. The reason for this is that the two flows could block each other if deployed on the same instance as there is only a single logical pipeline per Logstash instance.

---

<div class="post-metadata">

**Author:** ![yuanlinios](https://avatars.discourse-cdn.com/v4/letter/y/db5fbb/32.png) [@yuanlinios](https://discuss.elastic.co/u/yuanlinios)\
**Post date:** [January 24, 2017, 8:59am UTC](https://discuss.elastic.co/t/question-about-shipping-instance-and-indexing-instance-in-scalable-deployment-of-logstash/72552/3 "2017-01-24T08:59:14Z")

</div>

Thank you for the explanation! It makes sense to me

---

<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 21, 2017, 9:00am UTC](https://discuss.elastic.co/t/question-about-shipping-instance-and-indexing-instance-in-scalable-deployment-of-logstash/72552/4 "2017-02-21T09:00:02Z")

</div>

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