Thats not entirely true on how elasticsearch works. Basically, an index is
broken down into "replica sets" or partitions. By default, that number if
5. Each partition has at least one shard, and possible extra replicas. A
partition has an elected "primary" shard that all indexed go through it,
but then also applied to any replica shards.
Here is a simple video showing how it works:
Elasticsearch Platform — Find real-time answers at scale | Elastic.
And the berlin buzzwords talk that goes into more depth:
.
On Fri, Dec 30, 2011 at 5:25 PM, david@pilato.fr david@pilato.fr wrote:
**
I think that he is talking about primary shards (where Lucene does the
indexing job) vs. secondary shards (where you can perform searches).There could be only one shard elected as primary in an Elasticsearch
Cluster.So Indexing with Lucene is done in only one place for a given shard
instead.Shay, if I understood your berlin's talk, that's the way ES works for
indexing.Is that what you were talking about ?
David.
Le 30 décembre 2011 à 16:07, Shay Banon kimchy@gmail.com a écrit :
Not sure I understand the question... . When you create an index, you
specify the number of shards, and number of replicas. By default its 5
shards and 1 replica for each shard. So effectively each index is "multi
mastered".Note, I suspect that you are asking about multi master of an "index".
On Fri, Dec 30, 2011 at 4:24 PM, project2501 darreng5150@gmail.com
wrote:Hi,
Any plans for multimaster capability allowing high volume writes to
local nodes yet query across them as one?thanks.
--
David Pilato
http://dev.david.pilato.fr/
Twitter : @dadoonet