[
https://issues.apache.org/jira/browse/OOZIE-1877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14031548#comment-14031548
]
Shwetha G S commented on OOZIE-1877:
------------------------------------
There is some time difference between when oozie comes up and when safe mode is
enabled. The workflows can fail within this timeframe as well. Enabling safe
mode is again for advanced users.
If oozie fails at startup if hdfs is down, the error message can give option of
disabling the config if they understand what it means. The user can easily set
the config accordingly and can still bring up oozie. But if the sharelib is not
loaded and oozie doesn't complain at startup and later workflows start failing
with class not found exception, its difficult to figure out the reason. Another
option is to fail workflow launch itself. But its too much operational effort
of monitoring/re-running the killed ones.
> 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: Sub-task
> Reporter: Purshotam Shah
> Assignee: Purshotam Shah
> Attachments: OOZIE-1877-V1.patch
>
>
> "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)
