ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-12815) Change the default of topology.max.spout.pending from null to 1000 for Storm to prevent failures for Spout
Date Wed, 19 Aug 2015 11:21:45 GMT

    [ https://issues.apache.org/jira/browse/AMBARI-12815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14702865#comment-14702865
] 

Hadoop QA commented on AMBARI-12815:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12751254/AMBARI-12815.patch
  against trunk revision .

    {color:red}-1 patch{color}.  Top-level trunk compilation may be broken.

Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/3609//console

This message is automatically generated.

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

Mime
View raw message