# Elasticsearch Nodes Randomly Crashing Due to JVM Native Memory Allocation Failure on Windows Servers **URL:** \ **Category:** Elasticsearch\ **Tags:** runtime-fields\ **Created:** [May 20, 2026, 7:51am UTC](https://discuss.elastic.co/t/elasticsearch-nodes-randomly-crashing-due-to-jvm-native-memory-allocation-failure-on-windows-servers/386422 "2026-05-20T07:51:02Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![RainTown](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/raintown/32/140206_2.png) [@RainTown](https://discuss.elastic.co/u/RainTown)\ **Post date:** [May 20, 2026, 8:28am UTC](https://discuss.elastic.co/t/elasticsearch-nodes-randomly-crashing-due-to-jvm-native-memory-allocation-failure-on-windows-servers/386422/2 "2026-05-20T08:28:38Z")
> [@Shubham\_Khodpe](#): > > All Elasticsearch nodes randomly stop multiple times during operations such as indexing, shard relocation, and snapshot/archive activities. Is this the same cluster discussed in [your previous thread] ([Elasticsearch data node instability and indexing failures when using NAS (shared storage) with separate folders per node](https://discuss.elastic.co/t/elasticsearch-data-node-instability-and-indexing-failures-when-using-nas-shared-storage-with-separate-folders-per-node/385952)) ? In that thread, you had: > We are observing the following issues: > > - Bulk indexing failures (HTTP 500 errors) > - Errors such as: > - AlreadyClosedException: this ReferenceManager is closed > - RemoteTransportException > - UnavailableShardsException > > - Shards becoming unavailable intermittently > - Cluster not recovering properly at times > - Locking Issue > - Grafana dashboards taking a long time to load data If it is same cluster, how did you address the storage issues? --- _[View the full topic](https://discuss.elastic.co/t/elasticsearch-nodes-randomly-crashing-due-to-jvm-native-memory-allocation-failure-on-windows-servers/386422)._