rondagostino commented on PR #14400: URL: https://github.com/apache/kafka/pull/14400#issuecomment-1850870460
Thanks for describing the testing. I just did a test to see what would happen if the config file was specified with a relative path, and it did not work well. For example: # start broker in config/kraft directory, with relative path to config file ` ../../bin/kafka-server-start.sh broker.properties` ``` broker starts, as expected... ``` # try to stop it from repo top-level directory `bin/kafka-server-stop.sh --process-role=broker` ```zsh: no such file or directory: bin/kafka-server-stop.sh``` If we are supporting relative paths, then we need to fail elegantly and with. reasonable error message if we run the "stop" command from some other directory rather than the one where the node was started. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: jira-unsubscr...@kafka.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
