[
https://issues.apache.org/jira/browse/STORM-742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14482286#comment-14482286
]
ASF GitHub Bot commented on STORM-742:
--------------------------------------
Github user HeartSaVioR commented on the pull request:
https://github.com/apache/storm/pull/497#issuecomment-90296418
Thinking it once more, it cannot resolve @dashengju 's scenario from
STORM-738 since users can skip acking with NO-ACK mode.
I'll find alternative way to resolve it.
But PR can resolve ACK mode with too busy bolt, so this PR is still valid.
> Very busy ShellBolt subprocess cannot respond heartbeat just in time
> --------------------------------------------------------------------
>
> Key: STORM-742
> URL: https://issues.apache.org/jira/browse/STORM-742
> Project: Apache Storm
> Issue Type: Bug
> Affects Versions: 0.9.3, 0.10.0, 0.9.4, 0.11.0
> Reporter: Jungtaek Lim
> Assignee: Jungtaek Lim
> Priority: Critical
>
> As [~dashengju] stated from STORM-738, very busy ShellBolt subprocess cannot
> respond heartbeat just in time.
> Actually it's by design constraint (more details are on STORM-513 or
> STORM-738), but ShellSpout avoids constraint by updating heartbeat at any
> type of response from subprocess.
> We can apply this approach to ShellBolt and let ShellBolt avoid design
> constraint, too.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
