[
https://issues.apache.org/jira/browse/BIGTOP-689?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Shaposhnik updated BIGTOP-689:
------------------------------------
Attachment: BIGTOP-689.patch.txt
We can do a trivial change like the one in the attached patch, but my fear is
that since it is a Catalina-wide tmp directory won't Catalina itself clog
/var/lib/oozie with all sort of junk that Oozie scripts then would have to
clean up?
Now that I thought about it, shouldn't it be fixed upstream via introduction of
something like OOZIE_TMP location and a proper handling of its cleanup/creation
phase in upstream strartup scripts?
> Oozie use of /var/tmp in some CentOS versions create issues
> -----------------------------------------------------------
>
> Key: BIGTOP-689
> URL: https://issues.apache.org/jira/browse/BIGTOP-689
> Project: Bigtop
> Issue Type: Bug
> Components: RPM
> Affects Versions: 0.3.0
> Reporter: Alejandro Abdelnur
> Assignee: Roman Shaposhnik
> Attachments: BIGTOP-689.patch.txt
>
>
> It appears that centos is configured by default to clear /var/tmp every 30
> days
> Oozie creates some JAR files there at startup and uses them for the duration
> of the Oozie server process.
> Oozie should use a different TMP dir that is not cleaned up.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
