[
https://issues.apache.org/jira/browse/OOZIE-1877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14030314#comment-14030314
]
Purshotam Shah commented on OOZIE-1877:
---------------------------------------
Yes, most of the recent user will use sharelib, may not with the older version
where behavior was different.
Its not just about sharelib. Currently if sharelib at startup fails, then each
job submission will try to load sharelib. We also have sharelinupdate command.
If you put HDFS dependency with oozie, you have to always start HDFS before
starting oozie. You can't change the order.
You can't have an order where u start oozie and then HDFS.
It may not be acceptable to all users ( mainly ops).
> 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)
