ArafatKhan2198 opened a new pull request, #4308:
URL: https://github.com/apache/ozone/pull/4308

   ## What changes were proposed in this pull request?
   
   A lot of customers were facing issues Ozone service-related WebUI not 
opening with a 404 error. The issue can be fixed by restarting, but during the 
restart, a `jetty-0_0_0_0-*/webapp` folder is created, and the customer noticed 
that such a folder does not exist on the host with access issues. The customer 
performed manual restarts on each node and observed that the problem was 
resolved by creating a new `jetty-0_0_0_0-*/webapp` folder. 
   
   After investigating we 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.
   
   The main culprit for deletion is the 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.
   
   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.
   
   In case if this property is not set, then fall back to the default property.
   
   ## What is the link to the Apache JIRA
   https://issues.apache.org/jira/browse/HDDS-6176
   
   ## How was this patch tested?
   
   The Jetty directory got created in the desired location


-- 
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]

Reply via email to