# Windows 2012 Servers are not responding due to memory issue

**URL:** <https://discuss.elastic.co/t/windows-2012-servers-are-not-responding-due-to-memory-issue/70297>\
**Category:** Elasticsearch\
**Created:** [December 30, 2016, 8:07pm UTC](https://discuss.elastic.co/t/windows-2012-servers-are-not-responding-due-to-memory-issue/70297 "2016-12-30T20:07:02Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![dubul](https://avatars.discourse-cdn.com/v4/letter/d/9f8e36/32.png) [@dubul](https://discuss.elastic.co/u/dubul)\
**Post date:** [December 30, 2016, 8:07pm UTC](https://discuss.elastic.co/t/windows-2012-servers-are-not-responding-due-to-memory-issue/70297/1 "2016-12-30T20:07:02Z")

</div>

I have 3 windows servers with elastic search installed and clustered. These servers are not responding after 1 week, I cannot RDP into the vms. When I look into vsphere I notice that its utilizing max memory, So immediately I used to reboot the vms in vsphere. These VMs have 2 CPUs and 8GB Ram each, What is the recommended CPUs and RAM for ES servers(clustered-3)? This is the java memory set. Is there any problem with my java memorysetting or do I need to make changes in the yaml file? Can any one reply i'm facing this issue frequently.

![](https://us1.discourse-cdn.com/elastic/original/2X/7/7e338449aeb0b74151de7578e2f593b816aa60c8.png)

---

<div class="post-metadata">

**Author:** ![iluvcode](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/iluvcode/32/24929_2.png) [@iluvcode](https://discuss.elastic.co/u/iluvcode)\
**Post date:** [December 30, 2016, 8:14pm UTC](https://discuss.elastic.co/t/windows-2012-servers-are-not-responding-due-to-memory-issue/70297/2 "2016-12-30T20:14:58Z")

</div>

@dubul,

How did you configure your 3 node cluster?  
All 3 nodes Master and data nodes or 1 master and 2 data nodes?

---

<div class="post-metadata">

**Author:** ![dubul](https://avatars.discourse-cdn.com/v4/letter/d/9f8e36/32.png) [@dubul](https://discuss.elastic.co/u/dubul)\
**Post date:** [December 30, 2016, 9:08pm UTC](https://discuss.elastic.co/t/windows-2012-servers-are-not-responding-due-to-memory-issue/70297/3 "2016-12-30T21:08:10Z")

</div>

node.master: true  
node.data: true

I have selected both

---

<div class="post-metadata">

**Author:** ![dubul](https://avatars.discourse-cdn.com/v4/letter/d/9f8e36/32.png) [@dubul](https://discuss.elastic.co/u/dubul)\
**Post date:** [December 30, 2016, 9:12pm UTC](https://discuss.elastic.co/t/windows-2012-servers-are-not-responding-due-to-memory-issue/70297/4 "2016-12-30T21:12:36Z")

</div>

This is my es config file. This config will be similar on all the three nodes except the nodename and networkhost will be different.

```
     # ======================== Elasticsearch Configuration =========================
    #
    # NOTE: Elasticsearch comes with reasonable defaults for most settings.
    # Before you set out to tweak and tune the configuration, make sure you
    # understand what are you trying to accomplish and the consequences.
    #
    # The primary way of configuring a node is via this file. This template lists
    # the most important settings you may want to configure for a production cluster.
    #
    # Please see the documentation for further information on configuration options:
    # <http://www.elastic.co/guide/en/elasticsearch/reference/current/setup-configuration.html>
    #
    # ---------------------------------- Cluster -----------------------------------
    #
    # Use a descriptive name for your cluster:
    #
     cluster.name: elasticsearch
    #
    # ------------------------------------ Node ------------------------------------
    #
    # Use a descriptive name for the node:
    #
     node.name: dt1es01p01
     node.master: true 
     node.data: true
    #
    # Add custom attributes to the node:
    #
    # node.rack: r1
    #
    # ----------------------------------- Paths ------------------------------------
    #
    # Path to directory where to store the data (separate multiple locations by comma):
    #
     path.data: f:\esdata
    #
    # Path to log files:
    #
     path.logs: f:\eslogs
    #
    # ----------------------------------- Memory -----------------------------------
    #
    # Lock the memory on startup:
    #
    # bootstrap.mlockall: true
    #
    # Make sure that the `ES_HEAP_SIZE` environment variable is set to about half the memory
    # available on the system and that the owner of the process is allowed to use this limit.
    #
    # Elasticsearch performs poorly when the system is swapping the memory.
    #
    # ---------------------------------- Network -----------------------------------
    #
    # Set the bind address to a specific IP (IPv4 or IPv6):
    #
     network.host: dt1es01p01
    #
    # Set a custom port for HTTP:
    #
     http.port: 9200
    #
    # For more information, see the documentation at:
    # <http://www.elastic.co/guide/en/elasticsearch/reference/current/modules-network.html>
    #
    # --------------------------------- Discovery ----------------------------------
    #
    # Pass an initial list of hosts to perform discovery when new node is started:
    # The default list of hosts is ["127.0.0.1", "[::1]"]
    #
     discovery.zen.ping.unicast.hosts: ["dt1es01p01", "dt1es01p02", "dt1es01p03"]
    #
    # Prevent the "split brain" by configuring the majority of nodes (total number of nodes / 2 + 1):
    #
     discovery.zen.minimum_master_nodes: 2
    #
    # For more information, see the documentation at:
    # <http://www.elastic.co/guide/en/elasticsearch/reference/current/modules-discovery.html>
    #
    # ---------------------------------- Gateway -----------------------------------
    #
    # Block initial recovery after a full cluster restart until N nodes are started:
    #
    # gateway.recover_after_nodes: 3
    #
    # For more information, see the documentation at:
    # <http://www.elastic.co/guide/en/elasticsearch/reference/current/modules-gateway.html>
    #
    # ---------------------------------- Various -----------------------------------
    #
    # Disable starting multiple nodes on a single system:
    #
    # node.max_local_storage_nodes: 1
    #
    # Require explicit names when deleting indices:
    #
    # action.destructive_requires_name: true
```

---

<div class="post-metadata">

**Author:** ![iluvcode](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/iluvcode/32/24929_2.png) [@iluvcode](https://discuss.elastic.co/u/iluvcode)\
**Post date:** [December 30, 2016, 9:22pm UTC](https://discuss.elastic.co/t/windows-2012-servers-are-not-responding-due-to-memory-issue/70297/5 "2016-12-30T21:22:26Z")

</div>

@dubul,  
uncomment this setting bootstrap.mlockall: true in yaml file.  
Also change the Initial memory pool value to match with your Maximum memory pool.

---

<div class="post-metadata">

**Author:** ![dubul](https://avatars.discourse-cdn.com/v4/letter/d/9f8e36/32.png) [@dubul](https://discuss.elastic.co/u/dubul)\
**Post date:** [December 30, 2016, 9:28pm UTC](https://discuss.elastic.co/t/windows-2012-servers-are-not-responding-due-to-memory-issue/70297/6 "2016-12-30T21:28:59Z")

</div>

Thank you @iluvcode

---

<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:** [January 27, 2017, 9:29pm UTC](https://discuss.elastic.co/t/windows-2012-servers-are-not-responding-due-to-memory-issue/70297/7 "2017-01-27T21:29:02Z")

</div>

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