You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bigtop.apache.org by "Alejandro Abdelnur (JIRA)" <ji...@apache.org> on 2012/08/15 19:14:38 UTC
[jira] [Created] (BIGTOP-689) Oozie use of /var/tmp in some CentOS
versions create issues
Alejandro Abdelnur created BIGTOP-689:
-----------------------------------------
Summary: 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
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
[jira] [Updated] (BIGTOP-689) Oozie use of /var/tmp in some CentOS
versions create issues
Posted by "Roman Shaposhnik (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Commented] (BIGTOP-689) Oozie use of /var/tmp in some
CentOS versions create issues
Posted by "Alejandro Abdelnur (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BIGTOP-689?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13444549#comment-13444549 ]
Alejandro Abdelnur commented on BIGTOP-689:
-------------------------------------------
+1
> 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
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (BIGTOP-689) Oozie use of /var/tmp in some
CentOS versions create issues
Posted by "Alejandro Abdelnur (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BIGTOP-689?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13435309#comment-13435309 ]
Alejandro Abdelnur commented on BIGTOP-689:
-------------------------------------------
This seems to affect RightScale CentOS.
We would need to change {{/usr/lib/oozie/bin/oozie-env.sh}} file and change the value of {{CATALINA_TMPDIR|| to a location where there is no cleanup daemon. Just keep in mind that currently Oozie does not clean up files written in there, relies on the OS restarts for that.
In addition, we should get the Oozie daemons to do the clean up of this files on stop.
> 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
>
> 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
[jira] [Commented] (BIGTOP-689) Oozie use of /var/tmp in some
CentOS versions create issues
Posted by "Andrew Bayer (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BIGTOP-689?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13444546#comment-13444546 ]
Andrew Bayer commented on BIGTOP-689:
-------------------------------------
+1
> 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
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (BIGTOP-689) Oozie use of /var/tmp in some CentOS
versions create issues
Posted by "Roman Shaposhnik (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BIGTOP-689?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Roman Shaposhnik resolved BIGTOP-689.
-------------------------------------
Resolution: Fixed
Fix Version/s: 0.5.0
> 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
> Fix For: 0.5.0
>
> 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
For more information on JIRA, see: http://www.atlassian.com/software/jira