[
https://issues.apache.org/jira/browse/STORM-3058?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stig Rohde Døssing resolved STORM-3058.
---------------------------------------
Resolution: Not A Problem
[[email protected]] Happy to help. Going to close this issue, since it
sounds like your question was answered. Please feel free to reopen if you think
there's still something we should change or talk about here.
> set TOPOLOGY_MAX_SPOUT_PENDING to one,but can get more than one tuple in bolt
> -----------------------------------------------------------------------------
>
> Key: STORM-3058
> URL: https://issues.apache.org/jira/browse/STORM-3058
> Project: Apache Storm
> Issue Type: Bug
> Components: storm-kafka
> Affects Versions: 0.10.2
> Reporter: [email protected]
> Priority: Major
>
> Spout in the nextTuple may pull more than one kafka message, will remain in
> the _waitingToEmit, and then launch one by one, even if the
> TOPOLOGY_MAX_SPOUT_PENDING set to 1, when the first tuple is defeated, the
> bolt will still receive follow-up Message until _waitingToEmit is completely
> transmitted.
> This and I think TOPOLOGY_MAX_SPOUT_PENDING is not the same meaning, I hope
> that the message can be strictly processed one by one, my topology worker
> number, spout and bolt parallelism are set to 1
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)