[
https://issues.apache.org/jira/browse/AMBARI-11090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sumit Mohanty updated AMBARI-11090:
-----------------------------------
Description:
Oozie pid file delete is conditioned on a *not_if* that is incorrect.
Therefore, even if Oozie server is running the pid file will get deleted and am
attempt will be made to create another instance of the oozie server. The second
instance will fail but by then the pid file would have the wrong value.
This condition interferes with auto-recovery logic as Ambari thinks that Oozie
is not running but all attempts to start fails.
was:
Oozie pid file delete is conditioned on a *not_if* that is incorrect as well as
there is no support for *not_if* in the FileProvider. Therefore, even if Oozie
server is running the pid file will get deleted and am attempt will be made to
create another instance of the oozie server. The second instance will fail but
by then the pid file would have the wrong value.
This condition interferes with auto-recovery logic as Ambari thinks that Oozie
is not running but all attempts to start fails.
> Oozie start is not idempotent
> -----------------------------
>
> Key: AMBARI-11090
> URL: https://issues.apache.org/jira/browse/AMBARI-11090
> Project: Ambari
> Issue Type: Bug
> Components: stacks
> Affects Versions: 2.0.0
> Reporter: Sumit Mohanty
> Assignee: Sumit Mohanty
> Fix For: 2.1.0
>
>
> Oozie pid file delete is conditioned on a *not_if* that is incorrect.
> Therefore, even if Oozie server is running the pid file will get deleted and
> am attempt will be made to create another instance of the oozie server. The
> second instance will fail but by then the pid file would have the wrong value.
> This condition interferes with auto-recovery logic as Ambari thinks that
> Oozie is not running but all attempts to start fails.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
