# Description Failed to start elasticSearch source code compiling on Windows **URL:** \ **Category:** Elasticsearch\ **Created:** [August 2, 2021, 3:36am UTC](https://discuss.elastic.co/t/description-failed-to-start-elasticsearch-source-code-compiling-on-windows/280177 "2021-08-02T03:36:23Z")\ **Posts on this page:** 10\ **Page:** 1
**Author:** ![liuliugang](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/liuliugang/32/89053_2.png) [@liuliugang](https://discuss.elastic.co/u/liuliugang)\ **Post date:** [August 2, 2021, 3:36am UTC](https://discuss.elastic.co/t/description-failed-to-start-elasticsearch-source-code-compiling-on-windows/280177/1 "2021-08-02T03:36:23Z")
How do I set es.path.conf? Is there a file explaining the setting method of this parameter in the project? Please advise. Thank you ![2](https://us1.discourse-cdn.com/elastic/original/3X/6/d/6d23253fe3b7459eacbee9f728f195f86ec070b6.png) IntelliJ IDEA version:2021.1 Elasticsearch version:7.10.0 Jdk version:14.0.2 Gradle version:6.6.1 ---
**Author:** ![spinscale](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/spinscale/32/25011_2.png) [@spinscale](https://discuss.elastic.co/u/spinscale)\ **Post date:** [August 2, 2021, 7:34am UTC](https://discuss.elastic.co/t/description-failed-to-start-elasticsearch-source-code-compiling-on-windows/280177/2 "2021-08-02T07:34:51Z")
This is mainly expecting to be started via a packaged version of Elasticsearch and thus requires certain settings passed as arguments and properties. You could package Elasticsearch and connect via remote debugging or run Elasticsearch within an integration test (see the many tests ending on `IT` in the source). if you add some more context, we can maybe figure out the right way based on what you want to achieve. ---
**Author:** ![liuliugang](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/liuliugang/32/89053_2.png) [@liuliugang](https://discuss.elastic.co/u/liuliugang)\ **Post date:** [August 2, 2021, 7:41am UTC](https://discuss.elastic.co/t/description-failed-to-start-elasticsearch-source-code-compiling-on-windows/280177/3 "2021-08-02T07:41:46Z")
Do I need this configuration if I want to boot locally in Windows to learn the source code internal processing logic? ---
**Author:** ![spinscale](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/spinscale/32/25011_2.png) [@spinscale](https://discuss.elastic.co/u/spinscale)\ **Post date:** [August 2, 2021, 7:55am UTC](https://discuss.elastic.co/t/description-failed-to-start-elasticsearch-source-code-compiling-on-windows/280177/4 "2021-08-02T07:55:25Z")
This might help [elasticsearch/TESTING.asciidoc at master · elastic/elasticsearch · GitHub](https://github.com/elastic/elasticsearch/blob/master/TESTING.asciidoc#launching-and-debugging-from-an-ide) ---
**Author:** ![liuliugang](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/liuliugang/32/89053_2.png) [@liuliugang](https://discuss.elastic.co/u/liuliugang)\ **Post date:** [August 2, 2021, 9:00am UTC](https://discuss.elastic.co/t/description-failed-to-start-elasticsearch-source-code-compiling-on-windows/280177/5 "2021-08-02T09:00:08Z")
Thank you for your answer, but it seems that Windows local debug cannot be used, I would like to ask if there is another way to start Windows local debug ---
**Author:** ![spinscale](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/spinscale/32/25011_2.png) [@spinscale](https://discuss.elastic.co/u/spinscale)\ **Post date:** [August 2, 2021, 9:13am UTC](https://discuss.elastic.co/t/description-failed-to-start-elasticsearch-source-code-compiling-on-windows/280177/6 "2021-08-02T09:13:07Z")
Can you explain why the `./gradlew run --debug-jvm` way does not work for you? ---
**Author:** ![liuliugang](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/liuliugang/32/89053_2.png) [@liuliugang](https://discuss.elastic.co/u/liuliugang)\ **Post date:** [August 2, 2021, 9:42am UTC](https://discuss.elastic.co/t/description-failed-to-start-elasticsearch-source-code-compiling-on-windows/280177/7 "2021-08-02T09:42:53Z")
This command seems to only support debugging remote services ![1](https://us1.discourse-cdn.com/elastic/original/3X/b/a/baf29a6fabe10919b6acd1a106dd4d31a16f6379.png) ---
**Author:** ![spinscale](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/spinscale/32/25011_2.png) [@spinscale](https://discuss.elastic.co/u/spinscale)\ **Post date:** [August 2, 2021, 10:12am UTC](https://discuss.elastic.co/t/description-failed-to-start-elasticsearch-source-code-compiling-on-windows/280177/8 "2021-08-02T10:12:38Z")
Yes, this is how you can start debugging in the IDE, it's a common approach and many Elasticsearch developers do it this way - I still do not understand, what is the problem with this approach, please be a little bite more specific if something does not work as expected or why this approach is not working out for you. Thank you! ---
**Author:** ![liuliugang](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/liuliugang/32/89053_2.png) [@liuliugang](https://discuss.elastic.co/u/liuliugang)\ **Post date:** [August 4, 2021, 3:27am UTC](https://discuss.elastic.co/t/description-failed-to-start-elasticsearch-source-code-compiling-on-windows/280177/9 "2021-08-04T03:27:37Z")
Thank you for your answer, but I tried to use gradle remote debugging mode and directly run the source main function of these two ways failed, is there any authoritative reference to run the source main function directly? Maybe we are more inclined to the second debugging method. I asked some colleagues and they did not know what Gradle is. It is the first time I heard of Gradle ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [September 1, 2021, 3:28am UTC](https://discuss.elastic.co/t/description-failed-to-start-elasticsearch-source-code-compiling-on-windows/280177/10 "2021-09-01T03:28:01Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.