[
https://issues.apache.org/jira/browse/AMBARI-11435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14580988#comment-14580988
]
Hudson commented on AMBARI-11435:
---------------------------------
SUCCESS: Integrated in Ambari-trunk-Commit #2879 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/2879/])
AMBARI-11435. Tell Ambari the value of topology.max.replication.wait.time.sec
for Storm HA. Additional fix (dlysnichenko) (dlysnichenko:
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=e05ee943e513467b40830a2513c4e778221d3ea3)
*
ambari-server/src/main/resources/common-services/STORM/0.9.1.2.1/package/scripts/params_linux.py
*
ambari-server/src/main/resources/stacks/HDPWIN/2.3/services/STORM/configuration/storm-site.xml
*
ambari-server/src/main/resources/stacks/HDP/2.3/services/STORM/configuration/storm-site.xml
*
ambari-server/src/main/resources/common-services/STORM/0.9.1.2.1/package/scripts/params_windows.py
> 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
>
> Attachments: AMBARI-11435.patch, AMBARI-11435_additional_fixes.patch
>
>
> 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)
