[
https://issues.apache.org/jira/browse/STORM-266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14034443#comment-14034443
]
Robert Joseph Evans commented on STORM-266:
-------------------------------------------
[~parth.brahmbhatt] I guess I was not very clear. I would like to see us try
to get the exit code of the subprocess and report it somehow, just because the
exit code often has important information in it. Inside
ShellProcess.readShellMsg where it catches a NoOutputException it might be a
good place to do this, there may be others too. I don't care how we record it.
either logging it or including it as part of the exception should be fine.
> Improve debuggability of ShellBolt and ShellSpout
> -------------------------------------------------
>
> Key: STORM-266
> URL: https://issues.apache.org/jira/browse/STORM-266
> Project: Apache Storm (Incubating)
> Issue Type: Improvement
> Reporter: Robert Joseph Evans
>
> ShellBolt and ShellSpout are sometimes difficult to debug, especially when
> there are multiple instances running in under the same worker. It would be
> good to include the name of the bolt/spout in the logged messages, and
> probably the PID of the sub process too.
> In the case of errors it would be good for ShellProcess to try
> and get the exit code for the process, up to a timeout, and then get the
> contents of stderr. Also in the case of errors when wrapping the exceptions
> we probably want to include the name of the bolt/spout and the PID in the
> Exception message.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
