Replica assignement on the same host

Elastic Stack Elasticsearch
1

Hi,

I have an ES cluster with 12 data nodes spread on 6 servers (so 2 nodes per
server) and I saw that replicas of a shard can be allocated on the same
server(on each nodes hosted by a server)

To avoid this I haveset those parameters to the cluster:
node.host: <server_name>
cluster.routing.allocation.awareness.attributes: zone, host

But I'm wondering if there are not a specific parameter for this instead of
using clustering awareness allocation?

Nicolas

--
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/4d3924ab-77e4-49ef-9039-52df801ff46d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

2

That's the best method as per

Regards,
Mark Walkom

Infrastructure Engineer
Campaign Monitor
email: markw@campaignmonitor.com
web: www.campaignmonitor.com

On 29 August 2014 20:45, 'Nicolas Fraison' via elasticsearch <
elasticsearch@googlegroups.com> wrote:

Hi,

I have an ES cluster with 12 data nodes spread on 6 servers (so 2 nodes
per server) and I saw that replicas of a shard can be allocated on the same
server(on each nodes hosted by a server)

To avoid this I haveset those parameters to the cluster:
node.host: <server_name>
cluster.routing.allocation.awareness.attributes: zone, host

But I'm wondering if there are not a specific parameter for this instead
of using clustering awareness allocation?

Nicolas

--
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/4d3924ab-77e4-49ef-9039-52df801ff46d%40googlegroups.com
https://groups.google.com/d/msgid/elasticsearch/4d3924ab-77e4-49ef-9039-52df801ff46d%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/CAEM624YaxHLT%3DsptzqcSQw3i9u9oozO_2DstFJ6vCs-VC_bzOw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

3

The replica of a shard should never be on the same node as the primary.
Where did you notice this anomaly? What version are you using?

--
Ivan

On Fri, Aug 29, 2014 at 3:52 AM, Mark Walkom markw@campaignmonitor.com
wrote:

That's the best method as per
Elasticsearch Platform — Find real-time answers at scale | Elastic

Regards,
Mark Walkom

Infrastructure Engineer
Campaign Monitor
email: markw@campaignmonitor.com
web: www.campaignmonitor.com

On 29 August 2014 20:45, 'Nicolas Fraison' via elasticsearch <
elasticsearch@googlegroups.com> wrote:

Hi,

I have an ES cluster with 12 data nodes spread on 6 servers (so 2 nodes
per server) and I saw that replicas of a shard can be allocated on the same
server(on each nodes hosted by a server)

To avoid this I haveset those parameters to the cluster:
node.host: <server_name>
cluster.routing.allocation.awareness.attributes: zone, host

But I'm wondering if there are not a specific parameter for this instead
of using clustering awareness allocation?

Nicolas

--
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/4d3924ab-77e4-49ef-9039-52df801ff46d%40googlegroups.com
https://groups.google.com/d/msgid/elasticsearch/4d3924ab-77e4-49ef-9039-52df801ff46d%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/CAEM624YaxHLT%3DsptzqcSQw3i9u9oozO_2DstFJ6vCs-VC_bzOw%40mail.gmail.com
https://groups.google.com/d/msgid/elasticsearch/CAEM624YaxHLT%3DsptzqcSQw3i9u9oozO_2DstFJ6vCs-VC_bzOw%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/CALY%3DcQCFgA6FprUZ%2BZoYsB47N4f28pXSP4%2BGfdkRn_3L%3D_tXow%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

4

He's running multiple ES instances/nodes per physical, ie a VM or container
or just a second process, so I don't think it's primary and secondary on
the same ES instance.

Regards,
Mark Walkom

Infrastructure Engineer
Campaign Monitor
email: markw@campaignmonitor.com
web: www.campaignmonitor.com

On 30 August 2014 05:16, Ivan Brusic ivan@brusic.com wrote:

The replica of a shard should never be on the same node as the primary.
Where did you notice this anomaly? What version are you using?

--
Ivan

On Fri, Aug 29, 2014 at 3:52 AM, Mark Walkom markw@campaignmonitor.com
wrote:

That's the best method as per
Elasticsearch Platform — Find real-time answers at scale | Elastic

Regards,
Mark Walkom

Infrastructure Engineer
Campaign Monitor
email: markw@campaignmonitor.com
web: www.campaignmonitor.com

On 29 August 2014 20:45, 'Nicolas Fraison' via elasticsearch <
elasticsearch@googlegroups.com> wrote:

Hi,

I have an ES cluster with 12 data nodes spread on 6 servers (so 2 nodes
per server) and I saw that replicas of a shard can be allocated on the same
server(on each nodes hosted by a server)

To avoid this I haveset those parameters to the cluster:
node.host: <server_name>
cluster.routing.allocation.awareness.attributes: zone, host

But I'm wondering if there are not a specific parameter for this instead
of using clustering awareness allocation?

Nicolas

--
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/4d3924ab-77e4-49ef-9039-52df801ff46d%40googlegroups.com
https://groups.google.com/d/msgid/elasticsearch/4d3924ab-77e4-49ef-9039-52df801ff46d%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/CAEM624YaxHLT%3DsptzqcSQw3i9u9oozO_2DstFJ6vCs-VC_bzOw%40mail.gmail.com
https://groups.google.com/d/msgid/elasticsearch/CAEM624YaxHLT%3DsptzqcSQw3i9u9oozO_2DstFJ6vCs-VC_bzOw%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/CALY%3DcQCFgA6FprUZ%2BZoYsB47N4f28pXSP4%2BGfdkRn_3L%3D_tXow%40mail.gmail.com
https://groups.google.com/d/msgid/elasticsearch/CALY%3DcQCFgA6FprUZ%2BZoYsB47N4f28pXSP4%2BGfdkRn_3L%3D_tXow%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/CAEM624bMkjzG%3Db%3DaQdq0pd6khSsVi3BDgVa2AcChimiuxtneKA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

5

It's Friday. Can't read. Nevermind. :slight_smile:

On Fri, Aug 29, 2014 at 5:06 PM, Mark Walkom markw@campaignmonitor.com
wrote:

He's running multiple ES instances/nodes per physical, ie a VM or
container or just a second process, so I don't think it's primary and
secondary on the same ES instance.

Regards,
Mark Walkom

Infrastructure Engineer
Campaign Monitor
email: markw@campaignmonitor.com
web: www.campaignmonitor.com

On 30 August 2014 05:16, Ivan Brusic ivan@brusic.com wrote:

The replica of a shard should never be on the same node as the primary.
Where did you notice this anomaly? What version are you using?

--
Ivan

On Fri, Aug 29, 2014 at 3:52 AM, Mark Walkom markw@campaignmonitor.com
wrote:

That's the best method as per
Elasticsearch Platform — Find real-time answers at scale | Elastic

Regards,
Mark Walkom

Infrastructure Engineer
Campaign Monitor
email: markw@campaignmonitor.com
web: www.campaignmonitor.com

On 29 August 2014 20:45, 'Nicolas Fraison' via elasticsearch <
elasticsearch@googlegroups.com> wrote:

Hi,

I have an ES cluster with 12 data nodes spread on 6 servers (so 2 nodes
per server) and I saw that replicas of a shard can be allocated on the same
server(on each nodes hosted by a server)

To avoid this I haveset those parameters to the cluster:
node.host: <server_name>
cluster.routing.allocation.awareness.attributes: zone, host

But I'm wondering if there are not a specific parameter for this
instead of using clustering awareness allocation?

Nicolas

--
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/4d3924ab-77e4-49ef-9039-52df801ff46d%40googlegroups.com
https://groups.google.com/d/msgid/elasticsearch/4d3924ab-77e4-49ef-9039-52df801ff46d%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/CAEM624YaxHLT%3DsptzqcSQw3i9u9oozO_2DstFJ6vCs-VC_bzOw%40mail.gmail.com
https://groups.google.com/d/msgid/elasticsearch/CAEM624YaxHLT%3DsptzqcSQw3i9u9oozO_2DstFJ6vCs-VC_bzOw%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/CALY%3DcQCFgA6FprUZ%2BZoYsB47N4f28pXSP4%2BGfdkRn_3L%3D_tXow%40mail.gmail.com
https://groups.google.com/d/msgid/elasticsearch/CALY%3DcQCFgA6FprUZ%2BZoYsB47N4f28pXSP4%2BGfdkRn_3L%3D_tXow%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/CAEM624bMkjzG%3Db%3DaQdq0pd6khSsVi3BDgVa2AcChimiuxtneKA%40mail.gmail.com
https://groups.google.com/d/msgid/elasticsearch/CAEM624bMkjzG%3Db%3DaQdq0pd6khSsVi3BDgVa2AcChimiuxtneKA%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/CALY%3DcQA_uyaQGXdKQt8hZr1X-qq_%2Bm3Rh%2BCpG4Fg_wRqYhdN0Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.