[
https://issues.apache.org/jira/browse/STORM-266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Joseph Evans resolved STORM-266.
---------------------------------------
Resolution: Fixed
Fix Version/s: 0.9.3-incubating
Assignee: Parth Brahmbhatt
Thanks Parth,
I merged this into master.
> 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
> Assignee: Parth Brahmbhatt
> Fix For: 0.9.3-incubating
>
>
> 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)
