ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dmitro Lisnichenko" <dlysniche...@hortonworks.com>
Subject Review Request 34718: Tell Ambari the value of topology.max.replication.wait.time.sec for Storm HA
Date Wed, 27 May 2015 17:19:17 GMT

-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/34718/
-----------------------------------------------------------

Review request for Ambari and Vitalyi Brodetskyi.


Bugs: AMBARI-11435
    https://issues.apache.org/jira/browse/AMBARI-11435


Repository: ambari


Description
-------

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.


Diffs
-----

  ambari-server/src/main/resources/common-services/STORM/0.9.1.2.1/package/scripts/params_linux.py
41ea1ac 
  ambari-server/src/main/resources/stacks/HDP/2.3/services/STORM/configuration/storm-site.xml
373f408 
  ambari-server/src/main/resources/stacks/HDPWIN/2.3/services/STORM/configuration/storm-site.xml
373f408 
  ambari-web/app/controllers/main/host/details.js 034ceae 

Diff: https://reviews.apache.org/r/34718/diff/


Testing
-------

mvn clean test


Thanks,

Dmitro Lisnichenko


Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message