Zen vs ec2 discovery

Which (if any) of the parameters documented at
http://www.elasticsearch.org/guide/reference/modules/discovery/zen/ apply
when using the ec2 discovery mechanism
(http://www.elasticsearch.org/guide/reference/modules/discovery/ec2/)?

--
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.

Started a bounty for better documentation:

On Wednesday, August 21, 2013 10:31:55 AM UTC-7, Eric Jain wrote:

Which (if any) of the parameters documented at
http://www.elasticsearch.org/guide/reference/modules/discovery/zen/ apply
when using the ec2 discovery mechanism (
http://www.elasticsearch.org/guide/reference/modules/discovery/ec2/)?

--
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.

We ended up approaching this differently.

We just use plain old zen, but have some startup code that sets the aws
zone into an environment variable which we use only for balance allocation
awareness.

EC2 module seemed like overkill or maybe underkill because it didn't do
what we wanted. Unicast only has to reach one of the hosts in the cluster,
so we list a host from each zone. That way if any zone at all is up, all
the machines can find each other.

That is, if you know you're going to have at least 3 nodes in your cluster,
you can just list those 3 nodes in your config, and no matter how large
your cluster is, the cluster will find those nodes and bootstrap.

Just my $.02.

--
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.

On Fri, Aug 23, 2013 at 12:55 PM, Pierce Wetter obastard@gmail.com wrote:

We just use plain old zen,

I still haven't given up on the ec2 plugin; I replace all machines
quite often (incl each time I do a small update), so having an
automatic discovery mechanism simplifies things a lot! But if I can't
find proper documentation and get it to work more reliably, I'll need
to reconsider...

but have some startup code that sets the aws zone
into an environment variable which we use only for balance allocation awareness.

Ensuring that replicas are spread out across multiple zones seems like
a good idea; can you elaborate a bit how you accomplish this?

--
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.

Ensuring that replicas are spread out across multiple zones seems like
a good idea; can you elaborate a bit how you accomplish this?

It was stupidly easy with zen.

  1. Count the number of zones you have. Subtract 1. That's the number of replicas you want.

  2. Setup something on the host to put AWS_ZONE in an environment variable. Like something in rc.init. Our Ops guys did this when I asked, looks like its making an ec2 API call and pulling the zone out of the answer.

  3. In the config set:

cluster.routing.allocation.awareness.attributes: awszone

  1. Set awszone as a node attribute.

That was it.

--
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.

On Fri, Aug 23, 2013 at 7:08 PM, Pierce Wetter obastard@gmail.com wrote:

cluster.routing.allocation.awareness.attributes: awszone

Neat, thanks for the tip!

--
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.