[
https://issues.apache.org/jira/browse/HDDS-6176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17692309#comment-17692309
]
Mohammad Arafat Khan edited comment on HDDS-6176 at 2/22/23 6:18 PM:
---------------------------------------------------------------------
After Investigating, I can confirm that the ozone code is not responsible for
the deletion of the contents in the tmp directory. It appears that an external
program is responsible for the deletion.
As [~zhtttylzz] rightly suggested that the issue may be related to a Linux
program called *{{systemd-tmpfiles-clean.timer}}* . This program is designed to
clean up temporary files that are generated by the system. By default, it runs
daily and removes files and directories that are older than 3 days.
Then the *{{systemd-tmpfiles-clean.timer}}* program can potentially remove the
Jetty directory if it is older than the age limit set in the timer's
configuration. This could lead to disruptions in the Jetty server's operation
and cause issues for applications that depend on it.
To avoid this issue, it is recommended to configure Jetty to use a dedicated
directory for its temporary files and directories, rather than the system's
temporary directory. We can do this by changing the *{{ozone.http.basedir}}*
property in the Ozone Service Advanced Configuration Snippet for the
{*}{{ozone-conf/ozone-site.xml}} file{*}. It is suggested that this property
should be set to a directory such as *{{/data/ozone}}* that already exists and
has sufficient permissions in HDFS.
This modification has been successfully tested on a test machine.
cc: [~kkasawa]
was (Author: JIRAUSER284839):
After Investigating, I can confirm that the ozone code is not responsible for
the deletion of the contents in the tmp directory. It appears that an external
program is responsible for the deletion.
As [~zhtttylzz] rightly suggested that the issue may be related to a Linux
program called *{{systemd-tmpfiles-clean.timer}}* . This program is designed to
clean up temporary files that are generated by the system. By default, it runs
daily and removes files and directories that are older than 3 days.
Then the *{{systemd-tmpfiles-clean.timer}}* program can potentially remove the
Jetty directory if it is older than the age limit set in the timer's
configuration. This could lead to disruptions in the Jetty server's operation
and cause issues for applications that depend on it.
To avoid this issue, it is recommended to configure Jetty to use a dedicated
directory for its temporary files and directories, rather than the system's
temporary directory. We can do this by changing the *{{ozone.http.basedir}}*
property in the Ozone Service Advanced Configuration Snippet for the
{*}{{ozone-conf/ozone-site.xml}} file{*}. It is suggested that this property
should be set to a directory such as *{{/data/ozone}}* that already exists and
has sufficient permissions in HDFS.
This modification has been successfully tested on a test machine.
> Ozone service WebUI is not accessible with 404 error
> ----------------------------------------------------
>
> Key: HDDS-6176
> URL: https://issues.apache.org/jira/browse/HDDS-6176
> Project: Apache Ozone
> Issue Type: Bug
> Components: Ozone Recon
> Reporter: George Huang
> Assignee: Mohammad Arafat Khan
> Priority: Major
>
> ozone service related webUI is not accessible with 404 error.
> Check the recon host, the corresponding jetty directory under /tmp were
> disappeared for some reason. Restart recon will fix this problem. The
> corresponding jetty directory got recreated.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
