[
https://issues.apache.org/jira/browse/AMBARI-13297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14941486#comment-14941486
]
Hadoop QA commented on AMBARI-13297:
------------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12764769/AMBARI-13297.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{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/3896//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/3896//console
This message is automatically generated.
> change nimbus.monitor.freq.secs=120 in ambari
> ---------------------------------------------
>
> Key: AMBARI-13297
> URL: https://issues.apache.org/jira/browse/AMBARI-13297
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.1.2
> Reporter: Dmitry Lysnichenko
> Assignee: Dmitry Lysnichenko
> Fix For: 2.1.3
>
> Attachments: AMBARI-13297.patch
>
>
> we decided nimbus.monitor.freq.secs=120 and committed to 2.3-maint
> But found that on ambari installed clusters are having
> nimbus.monitor.freq.secs=10
> which many times causes storm-hive integration tests to fail.
> And mannually setting nimbus.monitor.freq.secs=120 and restarting nimbus
> causes tests to pass
> So change nimbus.monitor.freq.secs to 120
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
