You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2015/05/27 22:01:18 UTC
[jira] [Commented] (AMBARI-11435) Tell Ambari the value of
topology.max.replication.wait.time.sec for Storm HA
[ https://issues.apache.org/jira/browse/AMBARI-11435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14561610#comment-14561610 ]
Hudson commented on AMBARI-11435:
---------------------------------
FAILURE: Integrated in Ambari-trunk-Commit #2727 (See [https://builds.apache.org/job/Ambari-trunk-Commit/2727/])
AMBARI-11435. Tell Ambari the value of topology.max.replication.wait.time.sec for Storm HA (dlysnichenko) (dlysnichenko: http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=90bd51a81b7b93de3ed73d6f674fbc6c035786e8)
* ambari-server/src/main/resources/stacks/HDPWIN/2.3/services/STORM/configuration/storm-site.xml
* ambari-server/src/main/resources/common-services/STORM/0.9.1.2.1/package/scripts/params_linux.py
* ambari-server/src/main/resources/stacks/HDP/2.3/services/STORM/configuration/storm-site.xml
* ambari-web/app/controllers/main/host/details.js
> Tell Ambari the value of topology.max.replication.wait.time.sec for Storm HA
> ----------------------------------------------------------------------------
>
> Key: AMBARI-11435
> URL: https://issues.apache.org/jira/browse/AMBARI-11435
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Reporter: Dmitry Lysnichenko
> Assignee: Dmitry Lysnichenko
> Fix For: 2.1.0
>
>
> for some reason zookeeper watches are not fired right now when a new topology is added. So you should be setting topology.max.replication.wait.time.sec = -1 or set topology.max.replication.wait.time.sec > nimbus.code.sync.freq.secs.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)