ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dmytro Sen" <d...@hortonworks.com>
Subject Review Request 37609: Change the default of topology.max.spout.pending from null to 1000 for Storm to prevent failures for Spout
Date Wed, 19 Aug 2015 10:28:37 GMT

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

Review request for Ambari and Vitalyi Brodetskyi.


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


Repository: ambari


Description
-------

PROBLEM: The deployed kafkaspout showed "failures" in the Storm UI, however there were no
exceptions. The latency was high. Currently, topology.max.spout.pending is set to null via
ambari and if the topology does not override it, it will not be set.
At this point this can be set for kafkaspout configuration object in the topology code.


Diffs
-----

  ambari-server/src/main/resources/common-services/STORM/0.9.1.2.1/configuration/storm-site.xml
b1cf129 
  ambari-server/src/main/resources/stacks/HDP/2.1.GlusterFS/services/STORM/configuration/storm-site.xml
b02d23a 
  ambari-server/src/test/python/stacks/2.1/configs/secured-storm-start.json.orig 118520d 

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


Testing
-------

Unit tests passed


Thanks,

Dmytro Sen


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