Ingest Nodeedit

Elasticsearch will automatically re-route index requests to ingest nodes, however with some careful consideration you can optimise this path.

Custom indexing clientedit

Since Elasticsearch will automatically reroute ingest requests to ingest nodes, you don’t have to specify or configure any routing information. However, if you’re doing heavy ingestion and have dedicated ingest nodes, it makes sense to send index requests to these nodes directly, to avoid any extra hops in the cluster.

The simplest way to achieve this is to create a dedicated "indexing" client instance, and use it for indexing requests.

var pool = new StaticConnectionPool(new [] 
    new Uri("http://ingestnode1:9200"),
    new Uri("http://ingestnode2:9200"),
    new Uri("http://ingestnode3:9200")
var settings = new ConnectionSettings(pool);
var indexingClient = new ElasticClient(settings);

list of ingest nodes

Determining ingest capabilityedit

In complex cluster configurations it can be easier to use a sniffing connection pool along with a node predicate to filter out the nodes that have ingest capabilities. This allows you to customise the cluster and not have to reconfigure the client.

var pool = new SniffingConnectionPool(new [] 
    new Uri("http://node1:9200"),
    new Uri("http://node2:9200"),
    new Uri("http://node3:9200")
var settings = new ConnectionSettings(pool).NodePredicate(n => n.IngestEnabled); 
var indexingClient = new ElasticClient(settings);

list of cluster nodes

predicate to select only nodes with ingest capabilities