# Multi Node - Same Cluster Same hosts **URL:** \ **Category:** Elasticsearch\ **Created:** [September 10, 2017, 2:36pm UTC](https://discuss.elastic.co/t/multi-node-same-cluster-same-hosts/99974 "2017-09-10T14:36:49Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![naoy](https://avatars.discourse-cdn.com/v4/letter/n/bb73d2/32.png) [@naoy](https://discuss.elastic.co/u/naoy)\ **Post date:** [September 10, 2017, 2:36pm UTC](https://discuss.elastic.co/t/multi-node-same-cluster-same-hosts/99974/1 "2017-09-10T14:36:49Z")
Hello, On our Production Platform we have Heap troubles which obliges us to restart our cluster every 10days~ (Heap of each nodes increase to 100%, so timeout on all cluster etc...) data : 33TB, 700indx replicat 1 We don't know why we have this heap trouble (nothing very relevant on logs...) We have 3 master nodes and 6 datanodes on elastic 5.5.0, configured with 31gb Heap. As our servers have 256gb RAM, I think we can configure ES to have 2 datanodes on each datanodes servers, even if i see it's not recommended on PRODUCTION platform (with configuration node.max\_local\_storage\_nodes: 2). 1st : is it a good thing to do ? What are the recommended configurations for that (i didn't see anything on elastic documentation on that point) 2: How work shards allocation on that case ? (Are we sure there was not primary shards and secondary on 2 nodes of the same host/server ? FI: I test a configuration on vm, 2 systemd with different conf path /opt/application/elasticsearch/current/config/node01 and node02 with param max local storage but i'm not sure it will be the best things to do on production Best regards. ---
**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:** [September 11, 2017, 12:34am UTC](https://discuss.elastic.co/t/multi-node-same-cluster-same-hosts/99974/2 "2017-09-11T00:34:29Z")
1. It does mean you can use existing resources more efficiently 2. See [Shard Allocation Awareness | Elasticsearch Reference [5.5] | Elastic](https://www.elastic.co/guide/en/elasticsearch/reference/5.5/allocation-awareness.html) > [@naoy](#): > > We don't know why we have this heap trouble (nothing very relevant on logs...) What version are you on? How many shards? What monitoring do you have in place? ---
**Author:** ![naoy](https://avatars.discourse-cdn.com/v4/letter/n/bb73d2/32.png) [@naoy](https://discuss.elastic.co/u/naoy)\ **Post date:** [September 11, 2017, 8:15am UTC](https://discuss.elastic.co/t/multi-node-same-cluster-same-hosts/99974/3 "2017-09-11T08:15:54Z")
Hello and first of all thank you to answer on this topic 🙂 Version of the cluster : 5.5.0 3 master nodes, 6 datanodes, Heap configured 31gb Concerning data : 34.41TB, 746 indices, 8668 shards, 19 billions doc When one node seems to have a 100% heap, logs only shows timeout and all our Kibana have timeout (as to test cluster healthy , I believe it's make a \_nodes/status, so it's logical) We have several projects which inject data through a nginx reverse proxy which make a roudrobin on all workernodes. All workernodes also have nginx running on port 9200 to contact our authentication user + projects backend ( which rebalance on http port of worker, 9201 (and 9202 if we add new node) Heap percent of each Worker reach fast enough, which force us to restart cluster, every 10 days approximatly... If you have any comments on it, please don't hesitate ---
**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:** [September 11, 2017, 8:17am UTC](https://discuss.elastic.co/t/multi-node-same-cluster-same-hosts/99974/4 "2017-09-11T08:17:18Z")
> [@naoy](#): > > 8668 shards That is problematic given you only have 6 nodes. You should look to use `_shrink` to reduce that substantially, by half would be ideal. ---
**Author:** ![naoy](https://avatars.discourse-cdn.com/v4/letter/n/bb73d2/32.png) [@naoy](https://discuss.elastic.co/u/naoy)\ **Post date:** [September 11, 2017, 2:57pm UTC](https://discuss.elastic.co/t/multi-node-same-cluster-same-hosts/99974/5 "2017-09-11T14:57:14Z")
Humm, I can't do that, in fact we have several users with several projects and I can't shrink their data... ☹ ---
**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:** [September 11, 2017, 9:25pm UTC](https://discuss.elastic.co/t/multi-node-same-cluster-same-hosts/99974/6 "2017-09-11T21:25:24Z")
Why not? It has no impact on the data. ---
**Author:** ![mujtabahussain](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mujtabahussain/32/17514_2.png) [@mujtabahussain](https://discuss.elastic.co/u/mujtabahussain)\ **Post date:** [September 12, 2017, 1:46am UTC](https://discuss.elastic.co/t/multi-node-same-cluster-same-hosts/99974/7 "2017-09-12T01:46:12Z")
The data is not impacted at all, just how its distributed. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [October 10, 2017, 1:46am UTC](https://discuss.elastic.co/t/multi-node-same-cluster-same-hosts/99974/8 "2017-10-10T01:46:22Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.