# Fixing bugs on Elasticsearch code

**URL:** <https://discuss.elastic.co/t/fixing-bugs-on-elasticsearch-code/159432>\
**Category:** Elasticsearch\
**Created:** [December 4, 2018, 11:13pm UTC](https://discuss.elastic.co/t/fixing-bugs-on-elasticsearch-code/159432 "2018-12-04T23:13:10Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![dennysfredericci](https://avatars.discourse-cdn.com/v4/letter/d/c0e974/32.png) [@dennysfredericci](https://discuss.elastic.co/u/dennysfredericci)\
**Post date:** [December 4, 2018, 11:13pm UTC](https://discuss.elastic.co/t/fixing-bugs-on-elasticsearch-code/159432/1 "2018-12-04T23:13:10Z")

</div>

Hi Folks,

I would like to fix some issues, I cloned the repo from Github and the build was fine using Gradle.

I tried to run the main method at org.elasticsearch.bootstrap.Elasticsearch#main but i am struggling with configurations...

So, the question is, how to run Elasticsearch using IntelliJ ? Is there any Wiki for developers? Is there any default launcher or any easy way to run my changes?

Regards,  
Dennys Fredericci

---

<div class="post-metadata">

**Author:** ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)\
**Post date:** [December 5, 2018, 10:02am UTC](https://discuss.elastic.co/t/fixing-bugs-on-elasticsearch-code/159432/2 "2018-12-05T10:02:35Z")

</div>

I generally don't run Elasticsearch directly from the IDE, because you can only really run a single node like that which misses all the multi-node fun 🙂 and it generally expects to run as a standalone application so it's probably tricky to get it to work.

[TESTING.asciidoc](https://github.com/elastic/elasticsearch/blob/master/TESTING.asciidoc) describes some ways you can run a node. Remote debugging works, so you can start a node (or a whole cluster) from the command line and then attach the debugger later. Personally I don't often do this, I mostly use the IDE to run tests. The test framework is very featureful - some tests go so far as to start a whole cluster of nodes within a single JVM - and I find this a good way to explore things.

---

<div class="post-metadata">

**Author:** ![dennysfredericci](https://avatars.discourse-cdn.com/v4/letter/d/c0e974/32.png) [@dennysfredericci](https://discuss.elastic.co/u/dennysfredericci)\
**Post date:** [December 5, 2018, 5:53pm UTC](https://discuss.elastic.co/t/fixing-bugs-on-elasticsearch-code/159432/3 "2018-12-05T17:53:01Z")

</div>

Hi David,

Thank you for your quick answer,

Yeah looks like a really useful page!

Let's see 🙂

Thanks

---

<div class="post-metadata">

**Author:** ![dennysfredericci](https://avatars.discourse-cdn.com/v4/letter/d/c0e974/32.png) [@dennysfredericci](https://discuss.elastic.co/u/dennysfredericci)\
**Post date:** [December 5, 2018, 6:00pm UTC](https://discuss.elastic.co/t/fixing-bugs-on-elasticsearch-code/159432/4 "2018-12-05T18:00:06Z")

</div>

It is aliveeeeeee 😃

 ![24](https://us1.discourse-cdn.com/elastic/original/3X/9/4/946778a1bc24f8db098c90913971c92067c5e862.png)

---

<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 2, 2019, 6:00pm UTC](https://discuss.elastic.co/t/fixing-bugs-on-elasticsearch-code/159432/5 "2019-01-02T18:00:08Z")

</div>

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