sible? As far as I can tell, there
> was no external command at the time to kill the process.
>
> From: user@storm.apache.org At: 05/06/19 13:14:02
> To: user@storm.apache.org
> Subject: Re: Storm kill fails with exit code 143
>
> I would assume that what actually happened is that
ed out/was terminated. Is something like this
possible? As far as I can tell, there was no external command at the time to
kill the process.
From: user@storm.apache.org At: 05/06/19 13:14:02To: user@storm.apache.org
Subject: Re: Storm kill fails with exit code 143
I would assume that what actually h
I would assume that what actually happened is that most of your workers
don't manage to finish shutting down the worker gracefully, and so exit
with code 20 due to the 1 second time limit imposed by the shutdown hook.
One of your workers happened to run the entire shutdown sequence within the
1 sec
An exit code of 143 indicates a SIGTERM was received. (143 - 128 = 15).
It seems like something killed the shutdown script.
https://www.tldp.org/LDP/abs/html/exitcodes.html
On Sun, May 5, 2019 at 8:19 PM JF Chen wrote:
> Do you run your storm application on yarn?
>
> Regard,
> Junfeng Chen
>
>
Do you run your storm application on yarn?
Regard,
Junfeng Chen
On Mon, May 6, 2019 at 4:53 AM Mitchell Rathbun (BLOOMBERG/ 731 LEX) <
mrathb...@bloomberg.net> wrote:
> Recently our shutdown script failed when calling storm kill with a return
> code of 143. Typically this means that SIGTERM was
Recently our shutdown script failed when calling storm kill with a return code
of 143. Typically this means that SIGTERM was received and the process was
terminated. I see in https://issues.apache.org/jira/browse/STORM-2176 that it
is possible to get this exit code if a topology takes too long t
