# Running master nodes on application servers **URL:** \ **Category:** Elasticsearch\ **Created:** [October 18, 2014, 5:59am UTC](https://discuss.elastic.co/t/running-master-nodes-on-application-servers/20316 "2014-10-18T05:59:00Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![webish](https://avatars.discourse-cdn.com/v4/letter/w/919ad9/32.png) [@webish](https://discuss.elastic.co/u/webish)\ **Post date:** [October 18, 2014, 5:59am UTC](https://discuss.elastic.co/t/running-master-nodes-on-application-servers/20316/1 "2014-10-18T05:59:00Z")
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](mailto: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). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![Ivan](https://avatars.discourse-cdn.com/v4/letter/i/df788c/32.png) [@Ivan](https://discuss.elastic.co/u/Ivan)\ **Post date:** [October 18, 2014, 6:31pm UTC](https://discuss.elastic.co/t/running-master-nodes-on-application-servers/20316/2 "2014-10-18T18:31:03Z")
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](mailto: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](mailto: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) > [https://groups.google.com/d/msgid/elasticsearch/528e269a-f0bd-41a3-86cc-06bd40d502f9%40googlegroups.com?utm\_medium=email&utm\_source=footer](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](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](mailto: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](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](https://groups.google.com/d/optout). ---
**Author:** ![jprante](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jprante/32/44941_2.png) [@jprante](https://discuss.elastic.co/u/jprante)\ **Post date:** [October 18, 2014, 11:37pm UTC](https://discuss.elastic.co/t/running-master-nodes-on-application-servers/20316/3 "2014-10-18T23:37:27Z")
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](mailto: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](mailto: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) > [https://groups.google.com/d/msgid/elasticsearch/528e269a-f0bd-41a3-86cc-06bd40d502f9%40googlegroups.com?utm\_medium=email&utm\_source=footer](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](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](mailto: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](https://groups.google.com/d/msgid/elasticsearch/CAKdsXoEQaPo_0TXnVE1WHZnsvogvBmcMXfsspwH%2B2Pi1Lnmj1A%40mail.gmail.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 6, 2017, 12:55am UTC](https://discuss.elastic.co/t/running-master-nodes-on-application-servers/20316/4 "2017-07-06T00:55:17Z")