Re: ShellBolts and Heartbeats

[임정택 <ka...@gmail.com>]

Hi,

ShellSpout / ShellBolt will suicide itself when there's a heartbeat issue
from the subprocess, and Supervisor or Nimbus will relaunch ShellSpout /
ShellBolt eventually.

Btw, ShellSpout treats any messages from subprocess as heartbeat, so piling
up is not an issue. But, ShellBolt didn't take care of it now.
There're some other issues reported which cannot be resolved with multilang
heartbeat design constraint we currently have, so I'd like to change the
approach.

Please refer,
https://mail-archives.apache.org/mod_mbox/incubator-storm-user/201506.mbox/%3CCAF5108iiB0_+y_MzReVUF7LWDsQgyi9jFK1QNPAupYs6_xj-jw@mail.gmail.com%3E

Hope this helps.

Thanks,
Jungtaek Lim (HeartSaVioR)


2015-06-30 23:31 GMT+09:00 Casey McQuillan <CM...@restaurant.org>:

> Hello,
>
>
>
> We’re currently running storm with a number of multi-lang components.  Our
> current version is 0.9.3 which, by my understanding, requires the
> subprocess to send back a response to heartbeat tuples.  My question is,
> what is storm’s expected behavior when a subcomponent does not return a
> heartbeat? If, say, a single tuple takes an unusual amount of time to
> process, causing multiple heartbeats to pile up, how does Storm treat that
> subprocess?
>



-- 
Name : 임 정택
Blog : http://www.heartsavior.net / http://dev.heartsavior.net
Twitter : http://twitter.com/heartsavior
LinkedIn : http://www.linkedin.com/in/heartsavior