You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@storm.apache.org by "Abhishek (JIRA)" <ji...@apache.org> on 2017/02/27 14:17:45 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 ]
Abhishek updated STORM-2384:
----------------------------
Summary: Add a log statement when spout skips calling nextTuple. (was: Add a log statement when spouts skips calling nextTuple.)
> 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
>
> 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
(v6.3.15#6346)