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

Posted to issues@storm.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2018/10/22 19:27:06 UTC

[jira] [Updated] (STORM-2384) Add a log statement when spout skips calling nextTuple.

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

ASF GitHub Bot updated STORM-2384:
----------------------------------
    Labels: easyfix logging pull-request-available  (was: easyfix logging)

> Add a log statement when spout skips calling nextTuple.
> -------------------------------------------------------
>
>                 Key: STORM-2384
>                 URL: https://issues.apache.org/jira/browse/STORM-2384
>             Project: Apache Storm
>          Issue Type: Improvement
>          Components: storm-core
>            Reporter: Abhishek
>            Priority: Minor
>              Labels: easyfix, logging, pull-request-available
>          Time Spent: 1.5h
>  Remaining Estimate: 0h
>
> I have come across threads where people ask questions about a topology being stuck because the spout isn't emitting anything. Having spent considerable time debugging this myself, I think adding a log statement for the case when spout skips calling nextTuple() because maxSpoutPending is reached or because throttling is on could save many developer hours.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)