You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@ambari.apache.org by "Dmytro Sen (JIRA)" <ji...@apache.org> on 2015/08/19 12:27:46 UTC

[jira] [Updated] (AMBARI-12815) Change the default of topology.max.spout.pending from null to 1000 for Storm to prevent failures for Spout

     [ https://issues.apache.org/jira/browse/AMBARI-12815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dmytro Sen updated AMBARI-12815:
--------------------------------
    Attachment: AMBARI-12815.patch

> 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)