The delay in starting the new worker is probably caused by supervisor.worker.timeout.secs , which has default value = 30 seconds. Supervisor waits for this much time before it assumes worker is dead. This is good because due to numerous reason a live worker may not be able to send heartbeats at a consistent rate.
Thanks Parth On Dec 4, 2014, at 2:16 AM, yuhao <[email protected]> wrote: > I tried this: in an running topology, I killed a worker (by doing "kill" > command to the worker progress), then I found that it did restart the worker, > which however took a "staring" time. It seems not a hot backup. Is there > something like "worker swapping"? > -- CONFIDENTIALITY NOTICE NOTICE: This message is intended for the use of the individual or entity to which it is addressed and may contain information that is confidential, privileged and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient, you are hereby notified that any printing, copying, dissemination, distribution, disclosure or forwarding of this communication is strictly prohibited. If you have received this communication in error, please contact the sender immediately and delete it from your system. Thank You.
