[Feature Request] Make multi-node gradle test clusters work with IntelliJ debugger · opensearch-project/OpenSearch#19342

(5 留言) (0 反應) (1 負責人)Java (8,123 star) (1,505 fork)batch import

Buildenhancementgood first issue

描述

Is your feature request related to a problem? Please describe

When running local clusters with ./gradlew run you can provide -PnumNodes=<number of nodes> to run a cluster locally with more than one node. This is useful but unfortunately you can't use it with --debug-jvm. It'd be great if you could use both simultaneously.

Describe the solution you'd like

Currently it fails because each node expects a different debug server running on ports 5005, 5006, and 5007:

Running opensearch in debug mode (client), node{::runTask-0} expecting running debug server on port 5005
Running opensearch in debug mode (client), node{::runTask-1} expecting running debug server on port 5006
Running opensearch in debug mode (client), node{::runTask-2} expecting running debug server on port 5007

Maybe they could all point towards the same server at 5005?

Related component

Build

Describe alternatives you've considered

No response

Additional context

No response

貢獻者指南

技術棧: java
領域: build system
議題類型: feature
難度: 3
預計時間: half day
活動狀態: blocked
清晰度: clear
前置要求: Gradle knowledgeJava debuggingOpenSearch build setup
新手友善度: 40
研究方向: Investigate the Gradle task configuration for multi node clusters in the build scripts (likely build.gradle or related files). The current implementation assigns unique debug ports per node (5005, 5006, etc.). The goal is to allow all nodes to connect to the same debug port (e.g., 5005) when debug jvm is used. Review the task definitions and see if a shared property or argument can be set. There is an assignee on the issue, so coordinate with them to avoid duplication of effort.