ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dmitry Lysnichenko (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMBARI-13297) change nimbus.monitor.freq.secs=120 in ambari
Date Fri, 02 Oct 2015 13:50:26 GMT

     [ https://issues.apache.org/jira/browse/AMBARI-13297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Dmitry Lysnichenko updated AMBARI-13297:
----------------------------------------
    Affects Version/s: 2.1.2

> 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)

Mime
View raw message