sagarl wrote:
We have our ES cluster running on aws instances where nodes can
come and go. We would like to disable Shard reallocation on
cluster in Normal state so that Node going down should not
rebalance the shards.(Just to avoid unnecessary Network i/o).
If your shard topology is
sagarl wrote:
Drew, Sorry I din't get the part when you said There's nothing
wrong with having a yellow cluster And yes I agree ES does a
good job of rebalancing but just think of a case where you have
close to few hundred GBs of data per shard which will move
around the cluster even though
Lance Lakey wrote:
Leave port 9200 open to everything but only allow search
requests so that all web clients can access ES but can only
search
Configure application servers to use port 9500 to communicate
with ES Configure firewalls to only allow application servers
access to ES port 9500
shift wrote:
I am seeing a high number of rejections for the bulk thread pool
on a 32 core system. Should I leave the thread pool size fixed
to the # of cores and the default queue size at 50? Are these
rejections re-processed?
From my clients sending bulk documents (logstash), do I need
Greetings!
0.90.11 is out, with caching improvements and added visibility into
Lucene's memory use. We've also released what's hopefully going to be our
final RC before 1.0.0. Check here for more info:
http://www.elasticsearch.org/blog/0-90-11-1-0-0-rc2-released/
Thanks!
Elasticsearch
