Excluding a node from having primary shards

Elastic Stack Elasticsearch
1

Hey guys,

Is it possible to exclude a node from having primary shards? The use case
is to have a node at a remote location: The node should have replicas of
all the shards, but no indexing operations should be routed through it due
to latency, which is why the shards should never become primaries on that
node. I looked at the routing / allocation settings but they don't let me
control whether a node can be primary or not. Any ideas?

Thanks,
Thomas

--
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.
For more options, visit https://groups.google.com/groups/opt_out.

2

we don't have a notion for this at this point. The only way I see this
working is that you restrict the nodes in the remote location from
allocating anything until the primary is allocated and then allow
allocation for a certain index again and bump the number of replicas to > 0

simon

On Wednesday, August 28, 2013 10:27:16 AM UTC+2, Thomas S. wrote:

Hey guys,

Is it possible to exclude a node from having primary shards? The use case
is to have a node at a remote location: The node should have replicas of
all the shards, but no indexing operations should be routed through it due
to latency, which is why the shards should never become primaries on that
node. I looked at the routing / allocation settings but they don't let me
control whether a node can be primary or not. Any ideas?

Thanks,
Thomas

--
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.
For more options, visit https://groups.google.com/groups/opt_out.