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

Posted to dev@storm.apache.org by "Jungtaek Lim (JIRA)" <ji...@apache.org> on 2015/04/07 02:35:14 UTC

[jira] [Updated] (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:all-tabpanel ]

Jungtaek Lim updated STORM-742:
-------------------------------
    Summary: Very busy ShellBolt subprocess with ACK mode cannot respond heartbeat just in time  (was: Very busy ShellBolt subprocess cannot respond heartbeat just in time)

> 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)