# Specific node can not requsts from logstash

**URL:** <https://discuss.elastic.co/t/specific-node-can-not-requsts-from-logstash/51362>\
**Category:** Elasticsearch\
**Created:** [May 31, 2016, 2:40am UTC](https://discuss.elastic.co/t/specific-node-can-not-requsts-from-logstash/51362 "2016-05-31T02:40:10Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![mir](https://avatars.discourse-cdn.com/v4/letter/m/82dd89/32.png) [@mir](https://discuss.elastic.co/u/mir)\
**Post date:** [May 31, 2016, 2:40am UTC](https://discuss.elastic.co/t/specific-node-can-not-requsts-from-logstash/51362/1 "2016-05-31T02:40:10Z")

</div>

elasticsearch config is like this:

[NODE-1]  
[cluster.name](http://cluster.name): cluster-name  
[node.name](http://node.name): node-1  
node.master: true  
node.data: true  
network.host: NODEIP  
discovery.zen.ping.unicast.hosts: [NODE1IP, NODE2IP, NODE3IP, NODE4IP]

[NODE-2]  
[cluster.name](http://cluster.name): cluster-name  
[node.name](http://node.name): node-2  
node.master: true  
node.data: true  
network.host: NODEIP  
discovery.zen.ping.unicast.hosts: [NODE1IP, NODE2IP, NODE3IP, NODE4IP]

[NODE-3]  
[cluster.name](http://cluster.name): cluster-name  
[node.name](http://node.name): node-3  
node.master: true  
node.data: true  
network.host: NODEIP  
discovery.zen.ping.unicast.hosts: [NODE1IP, NODE2IP, NODE3IP, NODE4IP]  
[NODE-4]  
[cluster.name](http://cluster.name): cluster-name  
[node.name](http://node.name): node-4  
node.master: false  
node.data: false  
network.host: NODEIP  
discovery.zen.ping.unicast.hosts: [NODE1IP, NODE2IP, NODE3IP, NODE4IP]

and logstash output config is like this

elasticsearch {  
hosts =\> [NODE1IP:9200, NODE2IP:9200, NODE3IP:9200, NODE4IP:9200]  
index =\> "apache-access-%{+YYYY-MM-dd}"  
document\_type =\> "log"  
}

and I can find discovered all nodes in elastic logs.

But NODE4 is any requested from logstash  
( I confirm by threadpool API ( /\_cat/thread\_pool))

ip bulk.active bulk.queue bulk.rejected  
NODE1 8 9 24416  
NODE2 8 80 13819  
NODE3 0 0 16838  
NODE4 0 0 0

I don't know why help plz

---

<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 31, 2016, 3:29am UTC](https://discuss.elastic.co/t/specific-node-can-not-requsts-from-logstash/51362/2 "2016-05-31T03:29:57Z")

</div>

You don't appear to have `discovery.zen.ping.unicast.hosts` for the last node?

---

<div class="post-metadata">

**Author:** ![mir](https://avatars.discourse-cdn.com/v4/letter/m/82dd89/32.png) [@mir](https://discuss.elastic.co/u/mir)\
**Post date:** [May 31, 2016, 6:19am UTC](https://discuss.elastic.co/t/specific-node-can-not-requsts-from-logstash/51362/3 "2016-05-31T06:19:50Z")

</div>

Sorry It's just my typing miss.  
I set discovery.zen.ping.unicast.hosts: [NODE1IP, NODE2IP, NODE3IP, NODE4IP]  
on node4, too.

---

<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:** [June 1, 2016, 12:28am UTC](https://discuss.elastic.co/t/specific-node-can-not-requsts-from-logstash/51362/4 "2016-06-01T00:28:35Z")

</div>

Can you curl ES from the LS node?

---

<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:** [June 1, 2016, 5:19am UTC](https://discuss.elastic.co/t/specific-node-can-not-requsts-from-logstash/51362/5 "2016-06-01T05:19:23Z")

</div>

As NODE4 is a client node, it will distribute the work to the other nodes, where I assume it will be queued up.

---

<div class="post-metadata">

**Author:** ![mir](https://avatars.discourse-cdn.com/v4/letter/m/82dd89/32.png) [@mir](https://discuss.elastic.co/u/mir)\
**Post date:** [June 2, 2016, 1:45am UTC](https://discuss.elastic.co/t/specific-node-can-not-requsts-from-logstash/51362/6 "2016-06-02T01:45:54Z")

</div>

Yes, I alreay have checked it. Thank you

---

<div class="post-metadata">

**Author:** ![mir](https://avatars.discourse-cdn.com/v4/letter/m/82dd89/32.png) [@mir](https://discuss.elastic.co/u/mir)\
**Post date:** [June 2, 2016, 6:15am UTC](https://discuss.elastic.co/t/specific-node-can-not-requsts-from-logstash/51362/7 "2016-06-02T06:15:20Z")

</div>

Client node doesn't any indexing operation?

I can't understand which node(master, data, client) can accept indexing from LS? (I can't find any guide. I already read this [https://www.elastic.co/guide/en/elasticsearch/reference/2.3/modules-node.html](https://www.elastic.co/guide/en/elasticsearch/reference/2.3/modules-node.html) )

If I want to index directly to ES from LS,  
Which node I set elasticsearch's hosts info on LS?

---

<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:** [June 2, 2016, 6:21am UTC](https://discuss.elastic.co/t/specific-node-can-not-requsts-from-logstash/51362/8 "2016-06-02T06:21:12Z")

</div>

All nodes can accept indexing requests, but as client nodes do not hold any data, they will act as a load balancer and distribute the work it receives. The actual work is therefore done by the nodes holding data.

---

<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:47pm UTC](https://discuss.elastic.co/t/specific-node-can-not-requsts-from-logstash/51362/9 "2017-07-05T22:47:01Z")

</div>


