You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Dmitry Lysnichenko (JIRA)" <ji...@apache.org> on 2015/10/02 15:45:26 UTC
[jira] [Created] (AMBARI-13297) change nimbus.monitor.freq.secs=120
in ambari
Dmitry Lysnichenko created AMBARI-13297:
-------------------------------------------
Summary: 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
Reporter: Dmitry Lysnichenko
Assignee: Dmitry Lysnichenko
Attachments: AMBARI-13297.patch
As per https://hortonworks.jira.com/browse/BUG-43916:
In comment https://hortonworks.jira.com/browse/BUG-43916?focusedCommentId=282325&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-282325 and https://hortonworks.jira.com/browse/BUG-43916?focusedCommentId=282332&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-282332 following we decided nimbus.monitor.freq.secs=120 and committed to 2.3-maint -> https://github.com/hortonworks/storm/commit/5f7ef480c8ea225d5ec6c80dd3fc0fd59331c0a0#diff-cebb9e9e928119271a55620d525b79a6
But found that on ambari installed clusters are having nimbus.monitor.freq.secs=10 ->https://github.com/hortonworks/ambari/blob/apache-ref/branch-2.1.2/ambari-server/src/main/resources/common-services/STORM/0.9.1.2.1/configuration/storm-site.xml#L135-L136
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 in https://github.com/hortonworks/ambari/blob/apache-ref/branch-2.1.2/ambari-server/src/main/resources/common-services/STORM/0.9.1.2.1/configuration/storm-site.xml#L135-L136 change nimbus.monitor.freq.secs to 120
/cc [~schintalapani@hortonworks.com], kindly provide your feedback
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)