Why TransportClient only connect data nodes but ingest node when sniff set true?

If data nodes and ingest nodes are separated, TransportClient with sniff will first transport data to data node, then data node transport it to ingest node, after ETL transport back to data node.
Does it waste network bandwidth?

That's a valid concern. I don't have the answer though but may be @javanna knows if we can filter by node type.

Anyway, the Transport Client will be deprecated at some point so I'd encourage you switching to the Rest client. There is a sniffer as well and I did not see yet a way to filter nodes as well.

I'd suggest that you just provide the list of the ingest nodes. Or you can also have dedicated ingest nodes, data only nodes, master only nodes + coordinating only nodes. Which you would declare in that list of nodes.

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