You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@oozie.apache.org by "Purshotam Shah (JIRA)" <ji...@apache.org> on 2014/06/12 01:25:01 UTC
[jira] [Updated] (OOZIE-1877) Setting to fail oozie server startup
in case of sharelib misconfiguration
[ https://issues.apache.org/jira/browse/OOZIE-1877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Purshotam Shah updated OOZIE-1877:
----------------------------------
Description:
"OOZIE-1584 Setup sharelib using script and pickup latest(honor ship.launcher) and remove DFS dependency at startup" has removed sharelib dependency at startup.
If DFS is down or sharelib is misconfigured. Server will start without loading sharelib, admin can issue sharelibupdate command to load sharelib.
This is good, may not be acceptable in production. If sharelib is misconfigured then oozie server will come up without loading sharelib and all submitted hadoop job will fail.
Better to have a property to shutdown oozie server, if sharelib initialization fails.
> Setting to fail oozie server startup in case of sharelib misconfiguration
> -------------------------------------------------------------------------
>
> Key: OOZIE-1877
> URL: https://issues.apache.org/jira/browse/OOZIE-1877
> Project: Oozie
> Issue Type: Bug
> Reporter: Purshotam Shah
>
> "OOZIE-1584 Setup sharelib using script and pickup latest(honor ship.launcher) and remove DFS dependency at startup" has removed sharelib dependency at startup.
> If DFS is down or sharelib is misconfigured. Server will start without loading sharelib, admin can issue sharelibupdate command to load sharelib.
> This is good, may not be acceptable in production. If sharelib is misconfigured then oozie server will come up without loading sharelib and all submitted hadoop job will fail.
> Better to have a property to shutdown oozie server, if sharelib initialization fails.
--
This message was sent by Atlassian JIRA
(v6.2#6252)