# Full GC Allocation Failure **URL:** \ **Category:** Elasticsearch\ **Created:** [June 8, 2016, 7:25am UTC](https://discuss.elastic.co/t/full-gc-allocation-failure/52167 "2016-06-08T07:25:43Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![pecwich](https://avatars.discourse-cdn.com/v4/letter/p/bc79bd/32.png) [@pecwich](https://discuss.elastic.co/u/pecwich)\ **Post date:** [June 8, 2016, 7:25am UTC](https://discuss.elastic.co/t/full-gc-allocation-failure/52167/1 "2016-06-08T07:25:43Z")
Hi, My cluster just crashed and the error was showing full GC Allocation failure. What can be the reason?? ---
**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:** [June 8, 2016, 7:59am UTC](https://discuss.elastic.co/t/full-gc-allocation-failure/52167/2 "2016-06-08T07:59:10Z")
You haven't given much to work with here. What version are you on, java version? What other info can you give us? ---
**Author:** ![pecwich](https://avatars.discourse-cdn.com/v4/letter/p/bc79bd/32.png) [@pecwich](https://discuss.elastic.co/u/pecwich)\ **Post date:** [June 8, 2016, 8:53am UTC](https://discuss.elastic.co/t/full-gc-allocation-failure/52167/3 "2016-06-08T08:53:22Z")
Currently I am working on Elasticsearch 1.7. My hosts have 64Gb RAM, 30Gb of which is allocated to Heap. Lucene version 4.10.4. Why does this happen usually? ---
**Author:** ![jasontedor](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jasontedor/32/66992_2.png) [@jasontedor](https://discuss.elastic.co/u/jasontedor)\ **Post date:** [June 9, 2016, 2:30am UTC](https://discuss.elastic.co/t/full-gc-allocation-failure/52167/4 "2016-06-09T02:30:26Z")
> [@pecwich](#): > > My cluster just crashed and the error was showing full GC Allocation failure. What can be the reason?? Would it be possible for you to provide more detail? An allocation failure is an expected occurrence in a memory-managed language: it means that the heap is exhausted and it causes the memory manager to initiate a garbage collection cycle to free up space in the heap for the allocation request. So, this is normal behavior and it should not be the reported cause of a crash. Now, if the allocation failure triggers a garbage collection cycle and the memory manager is not able to evacuate enough heap for the requested allocation then the JVM will crash. But it will crash with an `OutOfMemoryError: Java heap space`. So, it would help to understand where you saw this message (it's normal to see in the garbage collection logs) and what message you actually saw on the crash. ---
**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:45pm UTC](https://discuss.elastic.co/t/full-gc-allocation-failure/52167/5 "2017-07-05T22:45:10Z")