You may want to do this for security though, no? Since ES does not have
authentication, SSL, etc. it may make sense to have a front end that is a no
data node, and keep ES data nodes behind a firewall, only accessible via the
mberkay on yahoo, google and skype
On Mon, Jan 31, 2011 at 3:11 PM, Shay Banon firstname.lastname@example.org:
In general, its a good practice to have all your nodes data nodes. If you
have a machine that is just hosting an HTTP ES proxy node (non data), then
its probably wasteful, and its better to have it as a data node to shared
On Monday, January 31, 2011 at 9:35 PM, Colin Surprenant wrote:
Thanks for your input.
Actually, what I am really wondering is the benefit of doing the
indexing on a non-data node. The documentation
explains well the benefit of running queries on a non-data node but
for indexing, is there a significant gain to run indexing requests on
a non-data node?
On Mon, Jan 31, 2011 at 12:49 PM, dbenson email@example.com wrote:
The best way to answer this is to run some load tests using your
incoming documents and your typical index queries.
We run four nodes all in a data configuration. We use the Java API for
indexing and searching. Our typical index load is 5-35 index requests
per second, this provides nearly no load. Our searches span multiple
indexes and have 10-25 criteria. Our search load is 100-150 queries/
sec against 31M docs, which we handle in the 34-40ms range.