Running master nodes on application servers

Elastic Stack Elasticsearch
1

I have a cluster of 3 r3.2xlarge aws servers. Each is a master and data
node.

Has anyone considered running a cluster of data nodes and then running
master nodes on each application server? Currently my application servers
have auto scaling policies.

The application server is pointing to a single ES node which isn't
distributing the load very well. Also, it has created a single point of
failure for the cluster.

I'm thinking to change the 3 r3.2xlarge servers to be data only nodes and
each app node would had it's own master node used to communicate with ES...

--
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/528e269a-f0bd-41a3-86cc-06bd40d502f9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

2

Is there some reason why your Elasticsearch nodes cannot serve as both
master and data? I believe that dedicated master nodes should only come
into play with large clusters, way beyond the 3 you have. If your master
nodes are tied to your app nodes, then I believe you will have less
resiliency since app servers are the ones the normally are rebooted in case
of issues.

--
Ivan

On Fri, Oct 17, 2014 at 10:59 PM, webish gregory@yoursports.com wrote:

I have a cluster of 3 r3.2xlarge aws servers. Each is a master and data
node.

Has anyone considered running a cluster of data nodes and then running
master nodes on each application server? Currently my application servers
have auto scaling policies.

The application server is pointing to a single ES node which isn't
distributing the load very well. Also, it has created a single point of
failure for the cluster.

I'm thinking to change the 3 r3.2xlarge servers to be data only nodes and
each app node would had it's own master node used to communicate with ES...

--
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/528e269a-f0bd-41a3-86cc-06bd40d502f9%40googlegroups.com
https://groups.google.com/d/msgid/elasticsearch/528e269a-f0bd-41a3-86cc-06bd40d502f9%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/CALY%3DcQD%2B0ZW%2B2uw%2BmrrinRZ6X%3DxMZhQ8iijbXFLyWr9_zZu_hg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

3

Why don't you point your application server to more than one ES node, by
using TransportClient?

Jörg

On Sat, Oct 18, 2014 at 7:59 AM, webish gregory@yoursports.com wrote:

I have a cluster of 3 r3.2xlarge aws servers. Each is a master and data
node.

Has anyone considered running a cluster of data nodes and then running
master nodes on each application server? Currently my application servers
have auto scaling policies.

The application server is pointing to a single ES node which isn't
distributing the load very well. Also, it has created a single point of
failure for the cluster.

I'm thinking to change the 3 r3.2xlarge servers to be data only nodes and
each app node would had it's own master node used to communicate with ES...

--
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/528e269a-f0bd-41a3-86cc-06bd40d502f9%40googlegroups.com
https://groups.google.com/d/msgid/elasticsearch/528e269a-f0bd-41a3-86cc-06bd40d502f9%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/CAKdsXoEQaPo_0TXnVE1WHZnsvogvBmcMXfsspwH%2B2Pi1Lnmj1A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.