Is bulk index sending to data nodes better or non-data nodes?

Elastic Stack Elasticsearch
1

Hello, anyone.
I used to setup some non-data nodes to accept bulk indexing from my
logstash/outputs/elasticsearch(http protocol). But some day I found one
article suggested use client node for searching but data node for bulk
indexing.

So, what's the best practical? Which node should we send bulk to,

master, data, client?

thanks~

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CABwsoohg%3Dh0WoC7p%3Do11whbEsBxjpiSXu%2BMVqnKKJYSrq7%3Dscw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

2

Which article is that?

It does not matter, you can send search and bulk requests to all nodes. ES
will do the routing and automatically forward the requests to the nodes
where they can be executed.

Jörg

On Mon, Mar 16, 2015 at 4:40 PM, chenlin rao rao.chenlin@gmail.com wrote:

Hello, anyone.
I used to setup some non-data nodes to accept bulk indexing from my
logstash/outputs/elasticsearch(http protocol). But some day I found one
article suggested use client node for searching but data node for bulk
indexing.

So, what's the best practical? Which node should we send bulk to,

master, data, client?

thanks~

--
You received this message because you are subscribed to the Google Groups
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/CABwsoohg%3Dh0WoC7p%3Do11whbEsBxjpiSXu%2BMVqnKKJYSrq7%3Dscw%40mail.gmail.com
https://groups.google.com/d/msgid/elasticsearch/CABwsoohg%3Dh0WoC7p%3Do11whbEsBxjpiSXu%2BMVqnKKJYSrq7%3Dscw%40mail.gmail.com?utm_medium=email&utm_source=footer
.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAKdsXoHMrNLSy8qUtNLrd0xNVyNdqThho4ySPVezxBNN%2BSpKjw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

3

It’s completely true that you can send requests to any node, however in practice one does not typically send requests directly to master nodes. It’s best to leave the master nodes alone so they can focus on maintaining global cluster state.

You can safely send bulk requests to either client or data nodes. The only difference is that the node that receives the request will sub-divide the bulk requests into per-node sub-bulk-requests and forward them on, then receive the results before sending back to the caller. In practice many people prefer to create a pool of client nodes and round-robin requests amongst them, never directly talking to the data nodes. Your mileage may vary, but this is a good rule of thumb and I would recommend following that general practice.

  • Andrew

On Mar 16, 2015, at 9:07 AM, joergprante@gmail.com wrote:

Which article is that?

It does not matter, you can send search and bulk requests to all nodes. ES will do the routing and automatically forward the requests to the nodes where they can be executed.

Jörg

On Mon, Mar 16, 2015 at 4:40 PM, chenlin rao <rao.chenlin@gmail.com mailto:rao.chenlin@gmail.com> wrote:
Hello, anyone.
I used to setup some non-data nodes to accept bulk indexing from my logstash/outputs/elasticsearch(http protocol). But some day I found one article suggested use client node for searching but data node for bulk indexing.

So, what's the best practical? Which node should we send bulk to, master, data, client?

thanks~

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com mailto:elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CABwsoohg%3Dh0WoC7p%3Do11whbEsBxjpiSXu%2BMVqnKKJYSrq7%3Dscw%40mail.gmail.com https://groups.google.com/d/msgid/elasticsearch/CABwsoohg%3Dh0WoC7p%3Do11whbEsBxjpiSXu%2BMVqnKKJYSrq7%3Dscw%40mail.gmail.com?utm_medium=email&utm_source=footer.
For more options, visit https://groups.google.com/d/optout https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com mailto:elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAKdsXoHMrNLSy8qUtNLrd0xNVyNdqThho4ySPVezxBNN%2BSpKjw%40mail.gmail.com https://groups.google.com/d/msgid/elasticsearch/CAKdsXoHMrNLSy8qUtNLrd0xNVyNdqThho4ySPVezxBNN%2BSpKjw%40mail.gmail.com?utm_medium=email&utm_source=footer.
For more options, visit https://groups.google.com/d/optout https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/A0F337FC-9993-47EC-AC29-5E287BE9332B%40elastic.co.
For more options, visit https://groups.google.com/d/optout.