# Pipeline.workers \> 1 does not result in parallel tcp output connections

**URL:** <https://discuss.elastic.co/t/pipeline-workers-1-does-not-result-in-parallel-tcp-output-connections/123110>\
**Category:** Logstash\
**Created:** [March 8, 2018, 3:29pm UTC](https://discuss.elastic.co/t/pipeline-workers-1-does-not-result-in-parallel-tcp-output-connections/123110 "2018-03-08T15:29:14Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![wyldfury](https://avatars.discourse-cdn.com/v4/letter/w/e9bcb4/32.png) [@wyldfury](https://discuss.elastic.co/u/wyldfury)\
**Post date:** [March 8, 2018, 3:29pm UTC](https://discuss.elastic.co/t/pipeline-workers-1-does-not-result-in-parallel-tcp-output-connections/123110/1 "2018-03-08T15:29:14Z")

</div>

Hi,

I have multiple pipelines configured with kafka input -\> tcp output (client). With pipeline.workers set to 1 for a pipeline, I see one long lived tcp connection to the configured server for the tcp output, which is unsurprising. When I increased pipeline.workers to 3 there's still just the one tcp connection. I'd like to put my remote servers behind a load balancer, but a single connection takes away a lot of the value there.

Is there any way to configure the tcp output to use more connections?

Thanks  
Guy

---

<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:** [April 5, 2018, 3:29pm UTC](https://discuss.elastic.co/t/pipeline-workers-1-does-not-result-in-parallel-tcp-output-connections/123110/2 "2018-04-05T15:29:29Z")

</div>

Closed on April 5, 2018, 3:29pm UTC

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