# Logstash and client nodes

**URL:** <https://discuss.elastic.co/t/logstash-and-client-nodes/51251>\
**Category:** Elasticsearch\
**Created:** [May 29, 2016, 3:15pm UTC](https://discuss.elastic.co/t/logstash-and-client-nodes/51251 "2016-05-29T15:15:32Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![tgdesrochers](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tgdesrochers/32/51322_2.png) [@tgdesrochers](https://discuss.elastic.co/u/tgdesrochers)\
**Post date:** [May 29, 2016, 3:15pm UTC](https://discuss.elastic.co/t/logstash-and-client-nodes/51251/1 "2016-05-29T15:15:32Z")

</div>

I have my ES cluster set up to accept among other things data shipped by logstash.

right now I have all my logstash nodes sending directly to my ES data nodes. My question is should I have my logstash nodes send to ES Client nodes? Would this give any performance boosts? Will it provide anything over having them talk directly to ES Data nodes?

Right now things run moderately well, I am just wondering if incorporating client nodes for applications to interact with the ES data cluster would be the optimal setup.

Thanks

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [May 29, 2016, 9:58pm UTC](https://discuss.elastic.co/t/logstash-and-client-nodes/51251/2 "2016-05-29T21:58:57Z")

</div>

The only thing it would do is reduce complexity as LS then just talks to `localhost`.

---

<div class="post-metadata">

**Author:** ![tgdesrochers](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tgdesrochers/32/51322_2.png) [@tgdesrochers](https://discuss.elastic.co/u/tgdesrochers)\
**Post date:** [May 29, 2016, 10:49pm UTC](https://discuss.elastic.co/t/logstash-and-client-nodes/51251/3 "2016-05-29T22:49:00Z")

</div>

Do you believe it could have any performance improvement?

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [May 30, 2016, 12:10am UTC](https://discuss.elastic.co/t/logstash-and-client-nodes/51251/4 "2016-05-30T00:10:01Z")

</div>

Maybe, you do talk to localhost, but then the client needs to forward it to the data node anyway. So you don't save a network hop at all.

Try it and see how it looks for your cluster!

---

<div class="post-metadata">

**Author:** ![tgdesrochers](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tgdesrochers/32/51322_2.png) [@tgdesrochers](https://discuss.elastic.co/u/tgdesrochers)\
**Post date:** [May 30, 2016, 1:26am UTC](https://discuss.elastic.co/t/logstash-and-client-nodes/51251/5 "2016-05-30T01:26:55Z")

</div>

I will add the es to the logstash nodes tomorrow.

A positive to it is I will be able to view my logstash nodes in marvel.  
Without running es on the node you can't see it in marvel. So there's an  
advantage.

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [May 30, 2016, 1:34am UTC](https://discuss.elastic.co/t/logstash-and-client-nodes/51251/6 "2016-05-30T01:34:54Z")

</div>

> [@tgdesrochers](#):
>
> Without running es on the node you can't see it in marvel.

That's not true, you still won't see LS in Marvel.

---

<div class="post-metadata">

**Author:** ![tgdesrochers](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tgdesrochers/32/51322_2.png) [@tgdesrochers](https://discuss.elastic.co/u/tgdesrochers)\
**Post date:** [May 30, 2016, 2:13am UTC](https://discuss.elastic.co/t/logstash-and-client-nodes/51251/7 "2016-05-30T02:13:41Z")

</div>

I didn't necessarily mean logstash the process more I'll see the nodes it's  
running on with marvel monitoring the es processes.

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [May 30, 2016, 2:18am UTC](https://discuss.elastic.co/t/logstash-and-client-nodes/51251/8 "2016-05-30T02:18:19Z")

</div>

Gotcha.  
In LS 5.0 we will have monitoring APIs that will be ingested into Marvel 🙂

---

<div class="post-metadata">

**Author:** ![tgdesrochers](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tgdesrochers/32/51322_2.png) [@tgdesrochers](https://discuss.elastic.co/u/tgdesrochers)\
**Post date:** [May 30, 2016, 12:53pm UTC](https://discuss.elastic.co/t/logstash-and-client-nodes/51251/9 "2016-05-30T12:53:01Z")

</div>

I saw that at the conference. I'm psyched for it. Can't wait to see the  
whole xpac

---

<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 5, 2017, 10:48pm UTC](https://discuss.elastic.co/t/logstash-and-client-nodes/51251/10 "2017-07-05T22:48:03Z")

</div>


