[
https://issues.apache.org/jira/browse/AMBARI-12815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14703497#comment-14703497
]
Hudson commented on AMBARI-12815:
---------------------------------
FAILURE: Integrated in Ambari-branch-2.1 #392 (See
[https://builds.apache.org/job/Ambari-branch-2.1/392/])
AMBARI-12815 Change the default of topology.max.spout.pending from null to 1000
for Storm to prevent failures for Spout (dsen) (dsen:
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=8aa706c8bdf777c03e646a3c3950e62b064ea08e)
*
ambari-server/src/main/resources/common-services/STORM/0.9.1.2.1/configuration/storm-site.xml
* ambari-server/src/test/python/stacks/2.1/configs/secured-storm-start.json.orig
*
ambari-server/src/main/resources/stacks/HDP/2.1.GlusterFS/services/STORM/configuration/storm-site.xml
> Change the default of topology.max.spout.pending from null to 1000 for Storm
> to prevent failures for Spout
> ----------------------------------------------------------------------------------------------------------
>
> Key: AMBARI-12815
> URL: https://issues.apache.org/jira/browse/AMBARI-12815
> Project: Ambari
> Issue Type: Bug
> Components: stacks
> Affects Versions: 2.0.0
> Reporter: Dmytro Sen
> Assignee: Dmytro Sen
> Priority: Critical
> Fix For: 2.1.2
>
> Attachments: AMBARI-12815.patch
>
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
