# How to increase heap size for local debugging running with build-tools

**URL:** <https://discuss.elastic.co/t/how-to-increase-heap-size-for-local-debugging-running-with-build-tools/196190>\
**Category:** Elasticsearch\
**Created:** [August 21, 2019, 8:26pm UTC](https://discuss.elastic.co/t/how-to-increase-heap-size-for-local-debugging-running-with-build-tools/196190 "2019-08-21T20:26:46Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![zcharli](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/zcharli/32/52338_2.png) [@zcharli](https://discuss.elastic.co/u/zcharli)\
**Post date:** [August 21, 2019, 8:26pm UTC](https://discuss.elastic.co/t/how-to-increase-heap-size-for-local-debugging-running-with-build-tools/196190/1 "2019-08-21T20:26:46Z")

</div>

I am trying to debug an ES plugin with build-tools and running into an out of heap error. I'm starting my debug with `./gradlew run`? Is there a way to to configure this per project?

Is this the right source for the run task?  
`org.elasticsearch.gradle.testclusters.ElasticsearchNode#startElasticsearchProcess`

The heap size is fixed to half a Gb. It would be nice to to make that configurable.

---

<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:** [September 18, 2019, 8:27pm UTC](https://discuss.elastic.co/t/how-to-increase-heap-size-for-local-debugging-running-with-build-tools/196190/2 "2019-09-18T20:27:01Z")

</div>

Closed on September 18, 2019, 8:27pm UTC

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