# Multiple ElasticSearch instances on Same Host in 2.1

**URL:** <https://discuss.elastic.co/t/multiple-elasticsearch-instances-on-same-host-in-2-1/37190>\
**Category:** Elasticsearch\
**Created:** [December 15, 2015, 2:08am UTC](https://discuss.elastic.co/t/multiple-elasticsearch-instances-on-same-host-in-2-1/37190 "2015-12-15T02:08:08Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![rahulnadella](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rahulnadella/32/22117_2.png) [@rahulnadella](https://discuss.elastic.co/u/rahulnadella)\
**Post date:** [December 15, 2015, 2:08am UTC](https://discuss.elastic.co/t/multiple-elasticsearch-instances-on-same-host-in-2-1/37190/1 "2015-12-15T02:08:08Z")

</div>

Trying to upgrade to ElasticSearch 2.1 with multiple instances on the same server (vertical scaling) but have run into issues with the inability to specify a CONF\_FILE anymore (2.0 release notes says it has been removed). I was able to deploy the multiple instances but am unable to set specific settings per node (i.e. cluster\_name, node name, shard\_size, replicas, etc) these values get set to the generated values from ElasticSearch. I have tried custom CONF\_FILE in different directories but get the same results.

I currently override the /etc/elasticsearch/elasticsearch.yml, /etc/elasticsearch/logging.yml, /etc/init.d/elasticsearch-a, /etc/sysconfig/ file, and /etc/security/limits.d/ file.

Is there a way to have these persist per node configuration (elasticsearch-a.yml, elasticsearch-b.yml, elasticsearch-c.yml, etc.)? I missing files that I need to update with the new 2.1 version.

---

<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:** [July 5, 2017, 11:31pm UTC](https://discuss.elastic.co/t/multiple-elasticsearch-instances-on-same-host-in-2-1/37190/2 "2017-07-05T23:31:05Z")

</div>