[
https://issues.apache.org/jira/browse/AMBARI-18919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15673593#comment-15673593
]
Hudson commented on AMBARI-18919:
---------------------------------
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6038 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/6038/])
AMBARI-18919. Oozie Server fails to start due to timeout (aonishuk) (aonishuk:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=675086954cb53db8821ac44f2ae8ef122f5dfec8])
* (edit)
ambari-server/src/main/resources/common-services/OOZIE/4.2.0.2.3/metainfo.xml
* (edit)
ambari-server/src/main/resources/common-services/OOZIE/4.0.0.2.0/metainfo.xml
> Oozie Server fails to start due to timeout
> ------------------------------------------
>
> Key: AMBARI-18919
> URL: https://issues.apache.org/jira/browse/AMBARI-18919
> Project: Ambari
> Issue Type: Bug
> Reporter: Andrew Onischuk
> Assignee: Andrew Onischuk
> Fix For: 2.5.0
>
> Attachments: AMBARI-18919.patch
>
>
> Because of slow env every operation took so much time:
>
>
> untar - 1min
> sharelib create - 7min
> start oozie cmd - 1min
> shareliblist hive - 7 min (was waitting for Oozie to actually start)
> hdfs directories copy - 3min
>
> Looks like we have to increase timeout here, so Oozie start can succeed on
> slow envs
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
