# Elastic 5.0 2 nodes cluster running on top of DC/OS 1.8.6

**URL:** <https://discuss.elastic.co/t/elastic-5-0-2-nodes-cluster-running-on-top-of-dc-os-1-8-6/66869>\
**Category:** Elasticsearch\
**Created:** [November 22, 2016, 2:49pm UTC](https://discuss.elastic.co/t/elastic-5-0-2-nodes-cluster-running-on-top-of-dc-os-1-8-6/66869 "2016-11-22T14:49:00Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![cruizpollino](https://avatars.discourse-cdn.com/v4/letter/c/6a8cbe/32.png) [@cruizpollino](https://discuss.elastic.co/u/cruizpollino)\
**Post date:** [November 22, 2016, 2:49pm UTC](https://discuss.elastic.co/t/elastic-5-0-2-nodes-cluster-running-on-top-of-dc-os-1-8-6/66869/1 "2016-11-22T14:49:00Z")

</div>

Good evening everyone,

My Name is Carlos Ruiz and I've set a DC/OS 1.8.6 lab environment with 3 masters and 3 agent nodes

One of the requirements we got from our customer is to be able to run a cluster with two instances of Elastic 5.x on different nodes.

I know that we can set such cluster running the task in dc/os setting

```
        discovery.zen.ping.unicast.hosts

```

parameter with the name of 2 of the 3 nodes and setting a constraint into those specific nodes, but the preferred option for scalability is to be able to set this configuration on a dynamic way

Have any of you made a configuration like this?, do you have any recipe that you can share or any reference link that I can use?

Thanks in advance for your help

Kind Regards

---

<div class="post-metadata">

**Author:** ![nik9000](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nik9000/32/44947_2.png) [@nik9000](https://discuss.elastic.co/u/nik9000)\
**Post date:** [November 22, 2016, 3:18pm UTC](https://discuss.elastic.co/t/elastic-5-0-2-nodes-cluster-running-on-top-of-dc-os-1-8-6/66869/2 "2016-11-22T15:18:58Z")

</div>

The usual thing to do is to set that parameter to all the master nodes. You can also use the [file discovery plugin](https://www.elastic.co/guide/en/elasticsearch/plugins/current/discovery-file.html) to read the hosts dynamically. I'm told that the file based plugin works well for folks in very dynamic environments.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [December 20, 2016, 3:19pm UTC](https://discuss.elastic.co/t/elastic-5-0-2-nodes-cluster-running-on-top-of-dc-os-1-8-6/66869/3 "2016-12-20T15:19:52Z")

</div>

Closed on December 20, 2016, 3:19pm UTC

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.
