From the documentation it's not clear if Cluster module allocation
awareness makes use of the fact that node is running in ec2 - which
seems natural to do.
So the question is do I need to set routing.allocation.awareness
explicitly like this:
cluster:
name: dev
routing.allocation.awareness:
attributes:
availability_zone
force.availability_zone.values: us-east-1a,us-
east-1c,us-east-1d
node:
availability_zone: us-east-1a
Or this could be simplified or completely omitted with same effect?
Like specifying node.availability_zone - seems to be unneeded - as we
already know such info from the ec2 discovery module.
Yes, you will need to explicitly set the awareness in the routing
allocation forced part. You can set cloud.node.auto_attributes to true and
it will automatically add the ec2 relevant (node.aws_availability_zone) to
the node attributes.
From the documentation it's not clear if Cluster module allocation
awareness makes use of the fact that node is running in ec2 - which
seems natural to do.
So the question is do I need to set routing.allocation.awareness
explicitly like this:
cluster:
name: dev
routing.allocation.awareness:
attributes:
availability_zone
force.availability_zone.values: us-east-1a,us-
east-1c,us-east-1d
node:
availability_zone: us-east-1a
Or this could be simplified or completely omitted with same effect?
Like specifying node.availability_zone - seems to be unneeded - as we
already know such info from the ec2 discovery module.
Yes, you will need to explicitly set the awareness in the routing
allocation forced part. You can set cloud.node.auto_attributes to true and
it will automatically add the ec2 relevant (node.aws_availability_zone) to
the node attributes.
From the documentation it's not clear if Cluster module allocation
awareness makes use of the fact that node is running in ec2 - which
seems natural to do.
So the question is do I need to set routing.allocation.awareness
explicitly like this:
cluster:
name: dev
routing.allocation.awareness:
attributes:
availability_zone
force.availability_zone.values: us-east-1a,us-
east-1c,us-east-1d
node:
availability_zone: us-east-1a
Or this could be simplified or completely omitted with same effect?
Like specifying node.availability_zone - seems to be unneeded - as we
already know such info from the ec2 discovery module.
Yes, you will need to explicitly set the awareness in the routing
allocation forced part. You can set cloud.node.auto_attributes to true
and
it will automatically add the ec2 relevant (node.aws_availability_zone)
to
the node attributes.
From the documentation it's not clear if Cluster module allocation
awareness makes use of the fact that node is running in ec2 - which
seems natural to do.
So the question is do I need to set routing.allocation.awareness
explicitly like this:
cluster:
name: dev
routing.allocation.awareness:
attributes:
availability_zone
force.availability_zone.values: us-east-1a,us-
east-1c,us-east-1d
node:
availability_zone: us-east-1a
Or this could be simplified or completely omitted with same effect?
Like specifying node.availability_zone - seems to be unneeded - as we
already know such info from the ec2 discovery module.
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.