# Converting from a single jvm per host to multi **URL:** \ **Category:** Elasticsearch\ **Created:** [March 8, 2017, 8:39pm UTC](https://discuss.elastic.co/t/converting-from-a-single-jvm-per-host-to-multi/77886 "2017-03-08T20:39:41Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![BS1](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/bs1/32/1718_2.png) [@BS1](https://discuss.elastic.co/u/BS1)\ **Post date:** [March 8, 2017, 8:39pm UTC](https://discuss.elastic.co/t/converting-from-a-single-jvm-per-host-to-multi/77886/1 "2017-03-08T20:39:41Z")
In a cluster with 20 servers @ 256GB RAM hosting a single JVM at 30G, what would be the procedure for converting to 4 JVMs per node ? If we take one host out, reconfigure it w/ the appropriate shard awareness stuff, and start up the 4 new instances, will Elasticsearch allocate 4x as many shards to this server, causing a hotspot until we can repeat for the rest of the servers ? ---
**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:** [March 8, 2017, 9:49pm UTC](https://discuss.elastic.co/t/converting-from-a-single-jvm-per-host-to-multi/77886/2 "2017-03-08T21:49:28Z")
It shouldn't immediately do that. Of course as you add more data it will. We don't really have a process for this, but what you've mentioned is ok. Just watch out if you change the data path, cause you may find your data "missing" if you change this/ ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [April 5, 2017, 9:49pm UTC](https://discuss.elastic.co/t/converting-from-a-single-jvm-per-host-to-multi/77886/3 "2017-04-05T21:49:36Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed. ---
**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:** [April 28, 2017, 11:15pm UTC](https://discuss.elastic.co/t/converting-from-a-single-jvm-per-host-to-multi/77886/4 "2017-04-28T23:15:09Z")
---
**Author:** ![BS1](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/bs1/32/1718_2.png) [@BS1](https://discuss.elastic.co/u/BS1)\ **Post date:** [May 19, 2017, 9:13pm UTC](https://discuss.elastic.co/t/converting-from-a-single-jvm-per-host-to-multi/77886/5 "2017-05-19T21:13:27Z")
Chiming in on this old thread with a summary of our findings: - when we added one multi-jvm server to the cluster, Elasticsearch did tread each JVM as a "regular" node and we ended up with 4x the data on this new server. - to combat this, we used the [watermark](https://www.elastic.co/guide/en/elasticsearch/reference/2.4/disk-allocator.html) setting to prevent too many shards from being allocated to the new node ---
**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, 10:00pm UTC](https://discuss.elastic.co/t/converting-from-a-single-jvm-per-host-to-multi/77886/6 "2017-07-05T22:00:14Z")