opensearch-project/OpenSearch

[Feature Request] Make multi-node gradle test clusters work with IntelliJ debugger

Open

#19,342 opened on Sep 19, 2025

View on GitHub
 (5 comments) (0 reactions) (1 assignee)Java (1,505 forks)batch import
Buildenhancementgood first issue

Repository metrics

Stars
 (8,123 stars)
PR merge metrics
 (Avg merge 5d 9h) (266 merged PRs in 30d)

Description

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

Contributor guide

Research direction
Investigate how the Gradle run task configures debug ports for multiple nodes. The current implementation assigns unique ports per node (5005, 5006, 5007). Explore options to either use a single debug port or allow configuration. Look at OpenSearch's Gradle scripts, specifically how ` debug jvm` and ` PnumNodes` interact.
Tech stack
java
Domain
backendbuild system
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
JavaGradle
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40