Question About Allocation of Primary and Replica Shards After Reboot

Just getting started with ElasticSearch, and I'm taking on a couple of
tasks as I get more familiar with it.

We recently restarted the six nodes in our ES cluster to perform the patch
for the Ghost vulnerability. We turned off reallocation, shut down the
individual nodes, then rebooted each node and turned reallocation back on.

We have 12 shards per index and one replica index. After the reboot of all
the nodes, we ended up with some nodes with three primary shards and one
replica index and some with three replicas and one primary shard.

Is there a way to prevent this mismatch in the distribution of our primary
and replica shards? Would like to have 2 primary shards and 2 replica shard
per node.

Also, is there a way to change a shard from a replica to a primary shard
without doing a relocation?

--
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/5ef0b6f3-6acf-4014-8746-1a7d236326e3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

It doesn't matter as long as your shard count is balanced.

The only difference between a primary and a replica is a flag that makes
the cluster see it as a primary. Any queries will use a primary or a
replica without concern.

On 11 February 2015 at 09:11, Josh Harris jharris@targetedvictory.com
wrote:

Just getting started with ElasticSearch, and I'm taking on a couple of
tasks as I get more familiar with it.

We recently restarted the six nodes in our ES cluster to perform the patch
for the Ghost vulnerability. We turned off reallocation, shut down the
individual nodes, then rebooted each node and turned reallocation back on.

We have 12 shards per index and one replica index. After the reboot of all
the nodes, we ended up with some nodes with three primary shards and one
replica index and some with three replicas and one primary shard.

Is there a way to prevent this mismatch in the distribution of our primary
and replica shards? Would like to have 2 primary shards and 2 replica shard
per node.

Also, is there a way to change a shard from a replica to a primary shard
without doing a relocation?

--
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/5ef0b6f3-6acf-4014-8746-1a7d236326e3%40googlegroups.com
https://groups.google.com/d/msgid/elasticsearch/5ef0b6f3-6acf-4014-8746-1a7d236326e3%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/CAEYi1X8bFZY%2B8QpmD1m52fQ5B%3DystN2i9LDCbKKniUUfTQ5QwA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Thanks for the reply.

An insert/update query will use a primary shard.

I've found one way only to rebalance the cluster - move a primary shard to
another node use reroute API, but it takes a while.
Is it possible to promote a replica shard as a primary?

On Tuesday, February 10, 2015 at 6:35:07 PM UTC-5, Mark Walkom wrote:

It doesn't matter as long as your shard count is balanced.

The only difference between a primary and a replica is a flag that makes
the cluster see it as a primary. Any queries will use a primary or a
replica without concern.

On 11 February 2015 at 09:11, Josh Harris <jha...@targetedvictory.com
<javascript:>> wrote:

Just getting started with ElasticSearch, and I'm taking on a couple of
tasks as I get more familiar with it.

We recently restarted the six nodes in our ES cluster to perform the
patch for the Ghost vulnerability. We turned off reallocation, shut down
the individual nodes, then rebooted each node and turned reallocation back
on.

We have 12 shards per index and one replica index. After the reboot of
all the nodes, we ended up with some nodes with three primary shards and
one replica index and some with three replicas and one primary shard.

Is there a way to prevent this mismatch in the distribution of our
primary and replica shards? Would like to have 2 primary shards and 2
replica shard per node.

Also, is there a way to change a shard from a replica to a primary shard
without doing a relocation?

--
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 elasticsearc...@googlegroups.com <javascript:>.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/5ef0b6f3-6acf-4014-8746-1a7d236326e3%40googlegroups.com
https://groups.google.com/d/msgid/elasticsearch/5ef0b6f3-6acf-4014-8746-1a7d236326e3%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/0eb22bc3-8d44-452e-be32-ed397a094bac%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Mark, to you point "...Any queries will use a primary or a replica without
concern."

I understand the indexing request will always be sent to the primary shard
first but aren't queries sent to Primary (just in case replica is
momentarily out of sync).

On Tue, Feb 10, 2015 at 3:34 PM, Mark Walkom markwalkom@gmail.com wrote:

It doesn't matter as long as your shard count is balanced.

The only difference between a primary and a replica is a flag that makes
the cluster see it as a primary. Any queries will use a primary or a
replica without concern.

On 11 February 2015 at 09:11, Josh Harris jharris@targetedvictory.com
wrote:

Just getting started with ElasticSearch, and I'm taking on a couple of
tasks as I get more familiar with it.

We recently restarted the six nodes in our ES cluster to perform the
patch for the Ghost vulnerability. We turned off reallocation, shut down
the individual nodes, then rebooted each node and turned reallocation back
on.

We have 12 shards per index and one replica index. After the reboot of
all the nodes, we ended up with some nodes with three primary shards and
one replica index and some with three replicas and one primary shard.

Is there a way to prevent this mismatch in the distribution of our
primary and replica shards? Would like to have 2 primary shards and 2
replica shard per node.

Also, is there a way to change a shard from a replica to a primary shard
without doing a relocation?

--
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/5ef0b6f3-6acf-4014-8746-1a7d236326e3%40googlegroups.com
https://groups.google.com/d/msgid/elasticsearch/5ef0b6f3-6acf-4014-8746-1a7d236326e3%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/CAEYi1X8bFZY%2B8QpmD1m52fQ5B%3DystN2i9LDCbKKniUUfTQ5QwA%40mail.gmail.com
https://groups.google.com/d/msgid/elasticsearch/CAEYi1X8bFZY%2B8QpmD1m52fQ5B%3DystN2i9LDCbKKniUUfTQ5QwA%40mail.gmail.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/CAH53p97D8FG7gwgoktkAR0Nj1M_0ZzC%3Dr5-VjxSYf98EqL271Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Take a look at
http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/docs-get.html#preference

On 11 February 2015 at 13:54, daaku gee daaqou@gmail.com wrote:

Mark, to you point "...Any queries will use a primary or a replica without
concern."

I understand the indexing request will always be sent to the primary shard
first but aren't queries sent to Primary (just in case replica is
momentarily out of sync).

On Tue, Feb 10, 2015 at 3:34 PM, Mark Walkom markwalkom@gmail.com wrote:

It doesn't matter as long as your shard count is balanced.

The only difference between a primary and a replica is a flag that makes
the cluster see it as a primary. Any queries will use a primary or a
replica without concern.

On 11 February 2015 at 09:11, Josh Harris jharris@targetedvictory.com
wrote:

Just getting started with ElasticSearch, and I'm taking on a couple of
tasks as I get more familiar with it.

We recently restarted the six nodes in our ES cluster to perform the
patch for the Ghost vulnerability. We turned off reallocation, shut down
the individual nodes, then rebooted each node and turned reallocation back
on.

We have 12 shards per index and one replica index. After the reboot of
all the nodes, we ended up with some nodes with three primary shards and
one replica index and some with three replicas and one primary shard.

Is there a way to prevent this mismatch in the distribution of our
primary and replica shards? Would like to have 2 primary shards and 2
replica shard per node.

Also, is there a way to change a shard from a replica to a primary shard
without doing a relocation?

--
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/5ef0b6f3-6acf-4014-8746-1a7d236326e3%40googlegroups.com
https://groups.google.com/d/msgid/elasticsearch/5ef0b6f3-6acf-4014-8746-1a7d236326e3%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/CAEYi1X8bFZY%2B8QpmD1m52fQ5B%3DystN2i9LDCbKKniUUfTQ5QwA%40mail.gmail.com
https://groups.google.com/d/msgid/elasticsearch/CAEYi1X8bFZY%2B8QpmD1m52fQ5B%3DystN2i9LDCbKKniUUfTQ5QwA%40mail.gmail.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/CAH53p97D8FG7gwgoktkAR0Nj1M_0ZzC%3Dr5-VjxSYf98EqL271Q%40mail.gmail.com
https://groups.google.com/d/msgid/elasticsearch/CAH53p97D8FG7gwgoktkAR0Nj1M_0ZzC%3Dr5-VjxSYf98EqL271Q%40mail.gmail.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/CAEYi1X8YLSNG9E6QjE_UMg%2BFh73kzk97%3DS-PPVXyRNK%3DV1r9qw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Thanks Mark, for sharing this document.

Regards
\d

On Tue, Feb 10, 2015 at 7:05 PM, Mark Walkom markwalkom@gmail.com wrote:

Take a look at
http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/docs-get.html#preference

On 11 February 2015 at 13:54, daaku gee daaqou@gmail.com wrote:

Mark, to you point "...Any queries will use a primary or a replica
without concern."

I understand the indexing request will always be sent to the primary
shard first but aren't queries sent to Primary (just in case replica is
momentarily out of sync).

On Tue, Feb 10, 2015 at 3:34 PM, Mark Walkom markwalkom@gmail.com
wrote:

It doesn't matter as long as your shard count is balanced.

The only difference between a primary and a replica is a flag that makes
the cluster see it as a primary. Any queries will use a primary or a
replica without concern.

On 11 February 2015 at 09:11, Josh Harris jharris@targetedvictory.com
wrote:

Just getting started with ElasticSearch, and I'm taking on a couple of
tasks as I get more familiar with it.

We recently restarted the six nodes in our ES cluster to perform the
patch for the Ghost vulnerability. We turned off reallocation, shut down
the individual nodes, then rebooted each node and turned reallocation back
on.

We have 12 shards per index and one replica index. After the reboot of
all the nodes, we ended up with some nodes with three primary shards and
one replica index and some with three replicas and one primary shard.

Is there a way to prevent this mismatch in the distribution of our
primary and replica shards? Would like to have 2 primary shards and 2
replica shard per node.

Also, is there a way to change a shard from a replica to a primary
shard without doing a relocation?

--
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/5ef0b6f3-6acf-4014-8746-1a7d236326e3%40googlegroups.com
https://groups.google.com/d/msgid/elasticsearch/5ef0b6f3-6acf-4014-8746-1a7d236326e3%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/CAEYi1X8bFZY%2B8QpmD1m52fQ5B%3DystN2i9LDCbKKniUUfTQ5QwA%40mail.gmail.com
https://groups.google.com/d/msgid/elasticsearch/CAEYi1X8bFZY%2B8QpmD1m52fQ5B%3DystN2i9LDCbKKniUUfTQ5QwA%40mail.gmail.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/CAH53p97D8FG7gwgoktkAR0Nj1M_0ZzC%3Dr5-VjxSYf98EqL271Q%40mail.gmail.com
https://groups.google.com/d/msgid/elasticsearch/CAH53p97D8FG7gwgoktkAR0Nj1M_0ZzC%3Dr5-VjxSYf98EqL271Q%40mail.gmail.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/CAEYi1X8YLSNG9E6QjE_UMg%2BFh73kzk97%3DS-PPVXyRNK%3DV1r9qw%40mail.gmail.com
https://groups.google.com/d/msgid/elasticsearch/CAEYi1X8YLSNG9E6QjE_UMg%2BFh73kzk97%3DS-PPVXyRNK%3DV1r9qw%40mail.gmail.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/CAH53p95qyFg-ZY%2BXmKVTaFtNB2HR%3DkYTwpUSPXVpdjdck76OBg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.