You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@storm.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2015/04/07 05:47:12 UTC
[jira] [Commented] (STORM-742) Very busy ShellBolt subprocess with
ACK mode cannot respond heartbeat just in time
[ https://issues.apache.org/jira/browse/STORM-742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14482527#comment-14482527 ]
ASF GitHub Bot commented on STORM-742:
--------------------------------------
Github user HeartSaVioR commented on the pull request:
https://github.com/apache/storm/pull/497#issuecomment-90348598
@dashengju
I filed new issue regarding very busy bolt with Non-ACK mode. https://issues.apache.org/jira/browse/STORM-758
Maybe you would be interested that instead of this, so please have a look at my idea in new issue.
Thanks!
> Very busy ShellBolt subprocess with ACK mode 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)