We currently are running dedicated master nodes but I believe they are also servicing queries. I can change it such that queries only hit the data nodes and see if that eliminates the issue...
On Monday, April 21, 2014 3:40:59 PM UTC-6, Binh Ly wrote: > > Other than network, is it possible that your nodes could sometimes be > overloaded such that they cannot respond immediately? If that's the case, > then you can probably get 3 nodes (servers), make them master-only nodes > (node.master: true, node.data: false). Set > discovery.zen.minimum_master_nodes: 2 for those 3 nodes. And then for the > rest of your other data nodes, make them non-master eligible (node.master: > false, node.data: true). This way you have 3 nodes dedicated only to do > cluster state/master tasks unimpeded by load or anything else other than > your network. Just don't run anything else on them or send queries/indexing > jobs to these 3 nodes. :) > -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/4858a2da-5ceb-48f1-8cfe-fe460ab2dcce%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
