[
https://issues.apache.org/jira/browse/AMBARI-18919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15673600#comment-15673600
]
Hadoop QA commented on AMBARI-18919:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12839352/AMBARI-18919.patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9309//console
This message is automatically generated.
> 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)
