You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "Aryan Gupta (Jira)" <ji...@apache.org> on 2026/07/19 20:59:00 UTC
[jira] [Updated] (HDDS-15912) HttpFS Gateway launcher should use runtime-managed log/temp dirs instead of OZONE_HOME paths
[ https://issues.apache.org/jira/browse/HDDS-15912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Aryan Gupta updated HDDS-15912:
-------------------------------
Description:
HttpFS launcher currently sets {{httpfs.log.dir}} and {{httpfs.temp.dir}} under {{OZONE_HOME}} ({{{}${OZONE_HOME}/log{}}}, {{{}${OZONE_HOME}/temp{}}}).
{{HttpFSServerWebApp}} initializes through {{{}ServerWebApp{}}}, and {{Server.init()}} validates these directories at startup. If {{${OZONE_HOME}/temp}} is missing, startup fails with {{{}S01: Dir .../temp does not exist{}}}, and Jetty stops the connector.
Fix: switch launcher defaults to runtime-managed directories:
* {{httpfs.log.dir=${OZONE_LOG_DIR}}}
* {{httpfs.temp.dir=${OZONE_PID_DIR}}}
This removes dependency on install-tree temp/log paths and makes HttpFS startup more robust across deployment layouts.
was:
HttpFS startup can fail in parcel deployments because the launcher sets {{httpfs.log.dir}} and {{httpfs.temp.dir}} under {{OZONE_HOME}} ({{{}${OZONE_HOME}/log{}}}, {{{}${OZONE_HOME}/temp{}}}). {{HttpFSServerWebApp}} still initializes through {{{}ServerWebApp{}}}, and {{Server.init()}} validates these directories. If {{${OZONE_HOME}/temp}} is missing, startup fails with {{{}S01: Dir .../temp does not exist{}}}, and Jetty stops the connector, making the HttpFS port unavailable.
Fix is to use runtime-managed launcher directories instead:
* {{httpfs.log.dir=${OZONE_LOG_DIR}}}
* {{httpfs.temp.dir=${OZONE_PID_DIR}}}
This avoids mutable runtime paths under install directory and keeps HttpFS startup stable across parcel/CM environments.
> HttpFS Gateway launcher should use runtime-managed log/temp dirs instead of OZONE_HOME paths
> --------------------------------------------------------------------------------------------
>
> Key: HDDS-15912
> URL: https://issues.apache.org/jira/browse/HDDS-15912
> Project: Apache Ozone
> Issue Type: Improvement
> Reporter: Aryan Gupta
> Assignee: Aryan Gupta
> Priority: Major
>
> HttpFS launcher currently sets {{httpfs.log.dir}} and {{httpfs.temp.dir}} under {{OZONE_HOME}} ({{{}${OZONE_HOME}/log{}}}, {{{}${OZONE_HOME}/temp{}}}).
> {{HttpFSServerWebApp}} initializes through {{{}ServerWebApp{}}}, and {{Server.init()}} validates these directories at startup. If {{${OZONE_HOME}/temp}} is missing, startup fails with {{{}S01: Dir .../temp does not exist{}}}, and Jetty stops the connector.
> Fix: switch launcher defaults to runtime-managed directories:
> * {{httpfs.log.dir=${OZONE_LOG_DIR}}}
> * {{httpfs.temp.dir=${OZONE_PID_DIR}}}
> This removes dependency on install-tree temp/log paths and makes HttpFS startup more robust across deployment layouts.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org