cryptoe opened a new pull request, #19709:
URL: https://github.com/apache/druid/pull/19709
The druid documentation mentions setting JAVA_HOME should be sufficient for
all druid processes to use the updated java versions.
The launched peons from the middle manager were not honoring that.
Added logic so that middle managers start honoring JAVA_HOME by using the
`bin/java` script which should be present in the working directory.
- When druid.indexer.runner.javaCommand is left at its default (java) and
bin/run-java exists in the working directory, the peon is launched via
bin/run-java (which resolves the java binary from
DRUID_JAVA_HOME → JAVA_HOME → PATH).
- Otherwise it falls back to the configured command (plain java by
default), so existing setups and explicit overrides are unaffected.
The existence check is reliable because peons inherit the parent process's
working directory. The default config value and docs remain java; the doc note
describes the auto-upgrade behavior.
--
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: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
