[
https://issues.apache.org/jira/browse/OOZIE-1877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14030887#comment-14030887
]
Rohini Palaniswamy commented on OOZIE-1877:
-------------------------------------------
Well I wanted it to fail on startup even initially. [~tucu00] did not want to
change the oozie behaviour where it can be started without hdfs being up. But
we faced issues during deployment with lot of workflows failing because of
misconfiguration. So we really need that feature and hence this new
configuration. The question now is to whether that behavior should be the
default or not. I don't have preference either way as our deployments are going
to have it set to true always. And in our case, Oozie is shutdown before they
shutdown the Namenode and started after cluster is upgraded. So we don't have
the case of namenode being down when Oozie is started. But not sure how other
deployments work and that needs to be considered.
[~rkanter],
[~shwethags]'s argument that it should be default so that general (not
advanced) users of Oozie don't waste time makes sense. Your thoughts? Would you
be open to making it false by default in your deployments and making it true as
default so it benefits most users?
> 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)
