# Using the Bulk Indexing API, if my node crashes, my elasticsearch heap memory does not get freed
**URL:** https://discuss.elastic.co/t/using-the-bulk-indexing-api-if-my-node-crashes-my-elasticsearch-heap-memory-does-not-get-freed/25839
**Category:** Elasticsearch
**Created:** [July 18, 2015, 3:54am UTC](https://discuss.elastic.co/t/using-the-bulk-indexing-api-if-my-node-crashes-my-elasticsearch-heap-memory-does-not-get-freed/25839 "2015-07-18T03:54:33Z")
**Posts on this page:** 7
**Page:** 1
### Author:  [@sahilc2200](https://discuss.elastic.co/u/sahilc2200)
#### Post date: [July 18, 2015, 3:54am UTC](https://discuss.elastic.co/t/using-the-bulk-indexing-api-if-my-node-crashes-my-elasticsearch-heap-memory-does-not-get-freed/25839/1 "2015-07-18T03:54:33Z")
So I am using the Bulk indexing API for ES 1.6. If a OOM occurs, then on restart, the node's heap does not get cleared for some reason. Then, OOM's occur much faster. I am not using any other queries except to index my documents, and I am running a two node cluster with 9GB allocated to each machine, and I have to index about 21M documents.
---
### Author:  [@warkolm](https://discuss.elastic.co/u/warkolm)
#### Post date: [July 18, 2015, 4:00am UTC](https://discuss.elastic.co/t/using-the-bulk-indexing-api-if-my-node-crashes-my-elasticsearch-heap-memory-does-not-get-freed/25839/2 "2015-07-18T04:00:10Z")
If it's still OOMing then you likely have too much data in there, but more information will help. However how much data is in the cluster?
---
### Author:  [@sahilc2200](https://discuss.elastic.co/u/sahilc2200)
#### Post date: [July 18, 2015, 5:28am UTC](https://discuss.elastic.co/t/using-the-bulk-indexing-api-if-my-node-crashes-my-elasticsearch-heap-memory-does-not-get-freed/25839/3 "2015-07-18T05:28:10Z")
The cluster actually has like 50 GB worth of data, and I am indexing about 150 documents at a time. Each document is about 4KB on average.
---
### Author:  [@warkolm](https://discuss.elastic.co/u/warkolm)
#### Post date: [July 18, 2015, 6:31am UTC](https://discuss.elastic.co/t/using-the-bulk-indexing-api-if-my-node-crashes-my-elasticsearch-heap-memory-does-not-get-freed/25839/4 "2015-07-18T06:31:04Z")
Then that's very odd.
If you start ES and then check `_cat/fielddata`, what does it report? Also, what's in your logs?
---
### Author:  [@sahilc2200](https://discuss.elastic.co/u/sahilc2200)
#### Post date: [July 18, 2015, 6:59am UTC](https://discuss.elastic.co/t/using-the-bulk-indexing-api-if-my-node-crashes-my-elasticsearch-heap-memory-does-not-get-freed/25839/5 "2015-07-18T06:59:22Z")
It tells me that there are 0b allocated for the fielddata. Is that supposed to happen? I am using ElasticHQ for monitoring the cluster, and it shows me that about 80% of the heap is occupied on node restart as well.
---
### Author:  [@warkolm](https://discuss.elastic.co/u/warkolm)
#### Post date: [July 18, 2015, 7:00am UTC](https://discuss.elastic.co/t/using-the-bulk-indexing-api-if-my-node-crashes-my-elasticsearch-heap-memory-does-not-get-freed/25839/6 "2015-07-18T07:00:29Z")
Are you using parent/child or nesting?
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [July 6, 2017, 12:00am UTC](https://discuss.elastic.co/t/using-the-bulk-indexing-api-if-my-node-crashes-my-elasticsearch-heap-memory-does-not-get-freed/25839/7 "2017-07-06T00:00:39Z")