Logstash should point to Master or Slave?


(Jibu Chacko) #1

ES:6.3.2

Below is my Master Conf

bootstrap.memory_lock: true

cluster.name: pm_production_elasticsearch

discovery.zen.minimum_master_nodes: 2

http.port: 9200

network.host: 0.0.0.0

node.data: false

node.master: true

transport.host: master1

transport.tcp.port: 9300

xpack.security.enabled: false

node.name: master1

discovery.zen.ping.unicast.hosts:

- master1:9300

- master2:9300

- master3:9300

Client Configs

bootstrap.memory_lock: true

cluster.name: pm_production_elasticsearch

discovery.zen.minimum_master_nodes: 2

http.port: 9200

network.host: 0.0.0.0

node.data: true

node.master: false

path.data: /data/elasticsearch, /data1/elasticsearch

transport.host: node_ip

transport.tcp.port: 9300

xpack.security.enabled: false

node.name: node_ip

discovery.zen.ping.unicast.hosts:

- master1:9300

- master2:9300

- master3:9300

I have logstash receiving input from filebeat and pushing to ES

What I want to know is can i push the output to the slave nodes or only the master nodes?


(Alexander Reelsen) #2

First, there are no slave nodes in Elasticsearch. There is a single active master node doing management work. This is also the reason, that you should point logstash to a so called data node or coordinating only node, that is not doing any master node work.

See https://www.elastic.co/guide/en/logstash/current/plugins-outputs-elasticsearch.html#plugins-outputs-elasticsearch-hosts


(Jibu Chacko) #3

@spinscale

So what is the significance of

node.data: false
node.master: true 

Is there a documention for the above parameters?


(Alexander Reelsen) #4

Yes, there is. See https://www.elastic.co/guide/en/elasticsearch/reference/6.4/modules-node.html


(system) #5

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