[
https://issues.apache.org/jira/browse/HIVE-18916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16515938#comment-16515938
]
Sahil Takiar commented on HIVE-18916:
-------------------------------------
[~aihuaxu] we actually already do that. There is an {{List}} called
{{childErrorLog}} which contains the STDERR. Unfortunately, even the STDERR
contains some extraneous information. For example, for the test
{{spark_submit_negative_executor_memory.q}} the {{childErrLog}} log is below:
{code
Run with --help for usage help or --verbose for debug output
Error: Executor Memory cores must be a positive number
{code}
Based on the Spark class {{org.apache.spark.util.CommandLineUtils}} errors
should usually start with "Error: "
> SparkClientImpl doesn't error out if spark-submit fails
> -------------------------------------------------------
>
> Key: HIVE-18916
> URL: https://issues.apache.org/jira/browse/HIVE-18916
> Project: Hive
> Issue Type: Sub-task
> Components: Spark
> Reporter: Sahil Takiar
> Assignee: Sahil Takiar
> Priority: Major
> Attachments: HIVE-18916.1.WIP.patch, HIVE-18916.2.patch,
> HIVE-18916.3.patch
>
>
> If {{spark-submit}} returns a non-zero exit code, {{SparkClientImpl}} will
> simply log the exit code, but won't throw an error. Eventually, the
> connection timeout will get triggered and an exception like {{Timed out
> waiting for client connection}} will be logged, which is pretty misleading.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
