[
https://issues.apache.org/jira/browse/AMBARI-18919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15673565#comment-15673565
]
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:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-server.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/9308//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9308//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)
