Skip to content

Fix stop-edge.bat to honor predefined IOTDB_HOME from environment - #19044

Open
siddiqueirshad wants to merge 1 commit into
apache:masterfrom
siddiqueirshad:fix-stop-edge-iotdb-home
Open

siddiqueirshad wants to merge 1 commit into
apache:masterfrom
siddiqueirshad:fix-stop-edge-iotdb-home

Conversation

@siddiqueirshad

Copy link
Copy Markdown

Description

In scripts/sbin/windows/start-edge.bat, stop-datanode.bat, and stop-standalone.bat, any existing IOTDB_HOME environment variable is honored using if NOT DEFINED IOTDB_HOME set "IOTDB_HOME=%cd%".
However, stop-edge.bat unconditionally executed set "IOTDB_HOME=%cd%". If an IoTDB Edge node was started with IOTDB_HOME set to an explicit path (e.g., via a symbolic link, junction, or custom configuration path), start-edge.bat launched the JVM process with -DIOTDB_HOME="..." using that environment variable, but stop-edge.bat overwrote IOTDB_HOME with the physical resolved path. This prevented stop-edge.bat from matching and stopping the running java.exe process.

Fixes #19005.

Changes

  • Updated scripts/sbin/windows/stop-edge.bat to check if NOT DEFINED IOTDB_HOME set "IOTDB_HOME=%cd%", consistent with start-edge.bat and the other Windows stop scripts.

Checklist

  • All commits signed off (git commit -s)
  • Verified behavior on Windows scripts

Signed-off-by: siddiqui irshad <mohdirshad1306@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

IoTDB Edge: stop-edge.bat ignores IOTDB_HOME, while start-edge.bat honours it

1 participant