[
https://issues.apache.org/jira/browse/SPARK-14110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tejas Patil updated SPARK-14110:
--------------------------------
Description: In case of failure in subprocess launched in PipedRDD, the
failure exception reads “Subprocess exited with status XXX”. Debugging this is
not easy for users especially if there are multiple pipe() operations in the
Spark application. It would be great to see the command of the failed
sub-process so that one can identify which pipe() failed. (was: In case of
failure in PipedRDD, the driver says “Subprocess exited with status XXX”.
Debugging this is not easy for users especially if there are multiple pipe()
operations in the Spark application. It would be great to see the command of
the failed sub-process so that one can identify which pipe() failed.)
> PipedRDD to print the command ran on failure
> --------------------------------------------
>
> Key: SPARK-14110
> URL: https://issues.apache.org/jira/browse/SPARK-14110
> Project: Spark
> Issue Type: Improvement
> Components: Spark Core
> Affects Versions: 1.6.1
> Reporter: Tejas Patil
> Priority: Trivial
>
> In case of failure in subprocess launched in PipedRDD, the failure exception
> reads “Subprocess exited with status XXX”. Debugging this is not easy for
> users especially if there are multiple pipe() operations in the Spark
> application. It would be great to see the command of the failed sub-process
> so that one can identify which pipe() failed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
