Chuanlei Ni created STORM-956:
---------------------------------
Summary: When the execute() or nextTuple() hang on external
resources, stop the Worker's heartbeat
Key: STORM-956
URL: https://issues.apache.org/jira/browse/STORM-956
Project: Apache Storm
Issue Type: Improvement
Reporter: Chuanlei Ni
Assignee: Chuanlei Ni
Priority: Minor
Sometimes the work threads produced by mk-threads in executor.clj hang on
external resources or other unknown reasons. This makes the workers stop
processing the tuples. I think it is better to kill this worker to resolve the
"hang". I plan to :
1. like `setup-ticks`, send a system-tick to receive-queue
2. the tuple-action-fn deal with this system-tick and remember the time that
processes this tuple in the executor-data
3. when worker do local heartbeat, check the time the executor writes to
executor-data. If the time is long from current (for example, 3 minutes), the
worker does not do the heartbeat. So the supervisor could deal with this
problem.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
