You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@storm.apache.org by "caofangkun (JIRA)" <ji...@apache.org> on 2014/10/14 13:46:43 UTC
[jira] [Updated] (STORM-532) Supervisor should restart worker
immediately, if the worker process does not exist any more
[ https://issues.apache.org/jira/browse/STORM-532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
caofangkun updated STORM-532:
-----------------------------
Description:
For now
if the worker process does not exist any more
Supervisor will have to wait a few seconds for worker heartbeart timeout and restart worker .
If supervisor knows the worker processid and check if the process exists in the sync-processes thread ,may need less time to restart worker.
1: record worker process id in the worker local heartbeart
2: in supervisor sync-processes ,get process id from worker local heartbeat
and check if the process exits
3: if not restart it immediately
was:
For now
if the worker process does not exist any more
Supervisor will have to wait a few seconds for worker heartbeart timeout and restart worker .
If supervisor knows the worker processid and check if the process exists in the sync-processes thread ,may need less time to restart worker.
1: record worker process id in the worker local heartbeart
2: in supervisor sync-processes ,get process id from worker local heartbeat
and check if the pricess exits
3: if not restart it immediately
> Supervisor should restart worker immediately, if the worker process does not exist any more
> --------------------------------------------------------------------------------------------
>
> Key: STORM-532
> URL: https://issues.apache.org/jira/browse/STORM-532
> Project: Apache Storm
> Issue Type: Improvement
> Affects Versions: 0.10.0
> Reporter: caofangkun
> Priority: Minor
>
> For now
> if the worker process does not exist any more
> Supervisor will have to wait a few seconds for worker heartbeart timeout and restart worker .
> If supervisor knows the worker processid and check if the process exists in the sync-processes thread ,may need less time to restart worker.
> 1: record worker process id in the worker local heartbeart
> 2: in supervisor sync-processes ,get process id from worker local heartbeat
> and check if the process exits
> 3: if not restart it immediately
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)