You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@storm.apache.org by "Rick Kellogg (JIRA)" <ji...@apache.org> on 2015/10/09 02:48:27 UTC

[jira] [Updated] (STORM-266) Improve debuggability of ShellBolt and ShellSpout

     [ https://issues.apache.org/jira/browse/STORM-266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rick Kellogg updated STORM-266:
-------------------------------
    Component/s: storm-multilang

> Improve debuggability of ShellBolt and ShellSpout
> -------------------------------------------------
>
>                 Key: STORM-266
>                 URL: https://issues.apache.org/jira/browse/STORM-266
>             Project: Apache Storm
>          Issue Type: Improvement
>          Components: storm-multilang
>            Reporter: Robert Joseph Evans
>            Assignee: Parth Brahmbhatt
>             Fix For: 0.9.3
>
>
> 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.3.4#6332)