[
https://issues.apache.org/jira/browse/AMBARI-11090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14541194#comment-14541194
]
Hudson commented on AMBARI-11090:
---------------------------------
FAILURE: Integrated in Ambari-trunk-Commit #2576 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/2576/])
AMBARI-11090. Oozie start is not idempotent (smohanty:
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=875bcfe4a4ebd78d4415d8d7ff6c2e6722a0fafb)
*
ambari-server/src/main/resources/common-services/OOZIE/4.0.0.2.0/package/scripts/oozie.py
* ambari-server/src/test/python/stacks/2.0.6/OOZIE/test_oozie_server.py
> 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
>
> Attachments: AMBARI-11090.patch, AMBARI-11090.with.ut.fixes.patch
>
>
> 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)
