[
https://issues.apache.org/jira/browse/AMBARI-13297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14944059#comment-14944059
]
Hudson commented on AMBARI-13297:
---------------------------------
SUCCESS: Integrated in Ambari-trunk-Commit #3598 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/3598/])
AMBARI-13297. change nimbus.monitor.freq.secs=120 in ambari (dlysnichenko:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=93f0896ec28a60a70e72ea9870374003fd2dcc90])
*
ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog213.java
*
ambari-server/src/main/java/org/apache/ambari/server/upgrade/SchemaUpgradeHelper.java
*
ambari-server/src/main/resources/common-services/STORM/0.9.1.2.1/configuration/storm-site.xml
* ambari-server/src/main/resources/stacks/HDP/2.2/upgrades/upgrade-2.3.xml
*
ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog213Test.java
> 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)
