# Elasticsearch - isolate master from data nodes **URL:** \ **Category:** Elasticsearch\ **Created:** [October 18, 2017, 1:36pm UTC](https://discuss.elastic.co/t/elasticsearch-isolate-master-from-data-nodes/104399 "2017-10-18T13:36:35Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![kochrist](https://avatars.discourse-cdn.com/v4/letter/k/ec9cab/32.png) [@kochrist](https://discuss.elastic.co/u/kochrist)\ **Post date:** [October 18, 2017, 1:36pm UTC](https://discuss.elastic.co/t/elasticsearch-isolate-master-from-data-nodes/104399/1 "2017-10-18T13:36:35Z")
I want to deploy elasticsearch on top of docker but I have only three VMs Which one is better? - One elasticsearch container on each VM with both master and data enabled? - Two elasticsearch containers on each VM one for master (only) and one for data (only)? I have the automation to support both, I just don't know if there is any _real_ benefit to isolate masters from data when they are on the same VM and what resources to allocate for each instance. ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [October 18, 2017, 1:46pm UTC](https://discuss.elastic.co/t/elasticsearch-isolate-master-from-data-nodes/104399/2 "2017-10-18T13:46:33Z")
> [@punkabbestia](#): > > I just don't know if there is any real benefit to isolate masters from data when they are on the same VM and what resources to allocate for each instance. At this smaller scale there's no real benefit. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [November 15, 2017, 1:46pm UTC](https://discuss.elastic.co/t/elasticsearch-isolate-master-from-data-nodes/104399/3 "2017-11-15T13:46:33Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.