Shards considered in write consistency

Elastic Stack Elasticsearch
1

Hey,

I have a question related to write consistency.

I have a elasticsearch cluster with 2 nodes. The nodes are configured as

number_of_shards = 5
number_of_replicas = 1

If i set the action.write_consistency value as quorum, what is the number
of active shards required to satisfy the quorum?
Please shed some light into the matter.

Thanks.

--
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/0029734f-7e86-47b5-8bf1-f0ebe6b6ad2a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

2

In your case quorum means that you need all primaries to be allocated.
Which is the case here.

Doc explains that very well: http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/docs-index_.html#index-consistency
Have a look in detail at: http://www.elasticsearch.org/guide/en/elasticsearch/guide/current/_how_primary_and_replica_shards_interact.html#_how_primary_and_replica_shards_interact
and http://www.elasticsearch.org/guide/en/elasticsearch/guide/current/distrib-write.html

HTH

--
David Pilato | Technical Advocate | Elasticsearch.com
@dadoonet | @elasticsearchfr

Le 2 juillet 2014 à 11:40:19, Varun Vasan V (varunvasan91@gmail.com) a écrit:

Hey,

I have a question related to write consistency.

I have a elasticsearch cluster with 2 nodes. The nodes are configured as

number_of_shards = 5
number_of_replicas = 1

If i set the action.write_consistency value as quorum, what is the number of active shards required to satisfy the quorum?
Please shed some light into the matter.

Thanks.

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/0029734f-7e86-47b5-8bf1-f0ebe6b6ad2a%40googlegroups.com.
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/etPan.53b3e296.257130a3.f8fb%40MacBook-Air-de-David.local.
For more options, visit https://groups.google.com/d/optout.

3

Thanks for your answer. Sorry for the late reply.

On Wed, Jul 2, 2014 at 4:14 PM, David Pilato david@pilato.fr wrote:

In your case quorum means that you need all primaries to be allocated.
Which is the case here.

Doc explains that very well:
Elasticsearch Platform — Find real-time answers at scale | Elastic
Have a look in detail at:
Elasticsearch Platform — Find real-time answers at scale | Elastic
and
Elasticsearch Platform — Find real-time answers at scale | Elastic

HTH

--
David Pilato | Technical Advocate | Elasticsearch.com
@dadoonet https://twitter.com/dadoonet | @elasticsearchfr
https://twitter.com/elasticsearchfr

Le 2 juillet 2014 à 11:40:19, Varun Vasan V (varunvasan91@gmail.com) a
écrit:

Hey,

I have a question related to write consistency.

I have a elasticsearch cluster with 2 nodes. The nodes are configured as

number_of_shards = 5
number_of_replicas = 1

If i set the action.write_consistency value as quorum, what is the
number of active shards required to satisfy the quorum?
Please shed some light into the matter.

Thanks.

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/0029734f-7e86-47b5-8bf1-f0ebe6b6ad2a%40googlegroups.com
https://groups.google.com/d/msgid/elasticsearch/0029734f-7e86-47b5-8bf1-f0ebe6b6ad2a%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 a topic in the
Google Groups "elasticsearch" group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/elasticsearch/2EXoj78nPuw/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/etPan.53b3e296.257130a3.f8fb%40MacBook-Air-de-David.local
https://groups.google.com/d/msgid/elasticsearch/etPan.53b3e296.257130a3.f8fb%40MacBook-Air-de-David.local?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/CAP1maN7-t6qQHn_a5LTTWEQT0euqU3EnuggydnmBwExmf0iX8w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.