Jörg
I think that system should work only for a two nodes setup. Otherwise, how
can we be sure that when letting elastisearch put a replica everywhere it
wants, there's going to be a copy in the nodes tagged as "search". Say you
have three "indexing" nodes and three "searching" nodes, and you go through
the process described by you. You can be certain that your index is in the
"indexing" zone, but when you set up replica=1, you are not sure where
elasticsearch is going to locate the replicas. Unless, of course, that the
fact that you're pointing the search to a particular node will "force"
elasticsearch to put a replica there.
On Thu, Feb 6, 2014 at 2:27 PM, José de Zárate jzarate@gmail.com wrote:
Jörg
that's brilliant indeed.
Now I'm going to check again with the dev crew which was the reason we
couldn't do clusters when having so many indexes (around 1k), and see if
that can be solved with smart shard routing management. (I think it was
related to the fact that ES waste too much resources trying to determine
which node is responsible or master for which clients).--
uh, oh http://www.youtube.com/watch?v=GMD_T7ICL0o.
--
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 elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAKNaH0WU3pC_cS8YNOG9Y1%2B70sL4jTM59dzhXkaFABAYFWbZkg%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.