we tried setting up a cluster with three nodes a while ago. It didn't hold
up , we figured it was because we had about 1k small indices (5000 items
each)
I think it might be possible to set up a cluster with such a setup.
My first question is: what is that could make a cluster with the default
configuration (5 shards, 1 replica, auto-everything) fails when 1k indices
are in order?
- Could it be that it spends way too much resources in rebalancing the
10k shards that would arise from the standard 5shards+1replica config?
- Could it be that keeping track of so many indices namespaces is too
costly for a master node that already has around 330 data shards to take
care of?
I guess these two situations could be eased by:
- setting one or more non-data nodes, and mark all the data nodes as
"non master eligible" (I don't even know if this is possible)
- setting a 1shard+1replica config for the indices
What I really would like to know is how does the cluster works internally.
at least a few hints. I've read the reference upside down and also the
newly created guide, but unfortunately the cluster chapter are marked as
"TODO".
well, that was it . hope there is some sensible soul out there that throw
some bone at me :-)
--
uh, oh <http://www.youtube.com/watch?v=GMD_T7ICL0o>.
<http://www.defectivebydesign.org/no-drm-in-html5>
--
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/CAKNaH0WX46SDVY2tv5X7TPzYD3WFuGncTNgNxY3pCkrrFPp7fA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
