With this set up:
Server1 Server2
Primary Shard 1 Primary Shard 2
Replica Shard 1 Replica Shard 2
- If primary shard 1 failed, would replica shard 1 take over and become
primary shard 1?
- Is reading performance optimized from 2 primary shards on 2 separate
severs?
- With documentation stating "we would end up with two nodes having one
shard each, and one node doing double the work with two
shards."...specifically the "one node doing double the work with two
shards"....do they mean 1 server having a primary shard and a replica
shard?
Also,
Server1 Server2
Primary Shard 1 Primary Shard 2
Replica Shard 2 Replica Shard 1
- is this set up possible and would it be beneficial? If so, would I have
to manually assign the shards or is this how ES does it default wise with 2
servers and 2 shards?
- with this set up...if it is even possible...is there a read performance
from having Primary Shard 1 on server 1 and having Replica Shard 1 on
server 2?
--
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/3a16db74-e41f-469a-aecd-acf515074391%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Your second example is what elasticsearch will do by default. It will never
allocate a primary and replica for the same shard on the same node. In that
example if one of the nodes were to go down both primaries would move to
the remaining node and the replicas would be unallocated and the cluster
will have yellow status.
Kimbro
On Thu, Jan 22, 2015 at 9:30 AM, Darin Hensley darin.hensley@gmail.com
wrote:
With this set up:
Server1 Server2
Primary Shard 1 Primary Shard 2
Replica Shard 1 Replica Shard 2
- If primary shard 1 failed, would replica shard 1 take over and become
primary shard 1?
- Is reading performance optimized from 2 primary shards on 2 separate
severs?
- With documentation stating "we would end up with two nodes having one
shard each, and one node doing double the work with two
shards."...specifically the "one node doing double the work with two
shards"....do they mean 1 server having a primary shard and a replica
shard?
Also,
Server1 Server2
Primary Shard 1 Primary Shard 2
Replica Shard 2 Replica Shard 1
- is this set up possible and would it be beneficial? If so, would I have
to manually assign the shards or is this how ES does it default wise with 2
servers and 2 shards?
- with this set up...if it is even possible...is there a read performance
from having Primary Shard 1 on server 1 and having Replica Shard 1 on
server 2?
--
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/3a16db74-e41f-469a-aecd-acf515074391%40googlegroups.com
https://groups.google.com/d/msgid/elasticsearch/3a16db74-e41f-469a-aecd-acf515074391%40googlegroups.com?utm_medium=email&utm_source=footer
.
For more options, visit https://groups.google.com/d/optout.
--
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/CAA0DmXbmJBAFQgN8%2BKGmtsd8m6vnYYOhzCuczig9Y%2BSNbKnWCg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.