[
https://issues.apache.org/jira/browse/STORM-1707?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15260896#comment-15260896
]
ASF GitHub Bot commented on STORM-1707:
---------------------------------------
GitHub user ppoulosk opened a pull request:
https://github.com/apache/storm/pull/1370
[STORM-1707] Remove two minute timeout after worker launch
This is a logic change the removes the two minute wait after worker launch
in sync processes. Instead of sitting in a wait loop for all of the workers to
come up, SyncProcessEvent now checks to see if a worker is in the NOT-STARTED
state, and has elapsed the Config.SUPERVISOR_WORKER_START_TIMEOUT_SECS time.
If it has, it kills and cleans up the worker.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ppoulosk/storm STORM-1707
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/storm/pull/1370.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1370
----
commit 8c8f2126446b932c51cce66dd93ffcfb7e16fc8e
Author: Paul Poulosky <ppoul...@crawlcall.corp.ne1.yahoo.com>
Date: 2016-04-27T20:41:38Z
Remove two minute timeout after worker launch
----
> Improve supervisor latency by removing 2-min wait
> -------------------------------------------------
>
> Key: STORM-1707
> URL: https://issues.apache.org/jira/browse/STORM-1707
> Project: Apache Storm
> Issue Type: Improvement
> Reporter: Paul Poulosky
> Assignee: Paul Poulosky
>
> After launching workers, the supervisor waits up to 2 minutes synchronously
> for the workers to be "launched".
> We should remove this, and instead keep track of launch time, making the
> "killer" function smart enough to determine the difference between a worker
> that's still launching, one that's timed out, etc.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
