[
https://issues.apache.org/jira/browse/HIVE-16484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15977363#comment-15977363
]
Sahil Takiar commented on HIVE-16484:
-------------------------------------
Thanks Marcelo.
Attached a WIP patch to trigger a run of Hive QA. It sounds like
{{SparkLauncher}} may be a better way of submitting the Spark application going
forward. Until SPARK-11035 is completed, the {{SparkLauncher}} will still run
{{bin/spark-submit}} but at least in its current state the {{SparkLauncher}}
handles all the complexity of running {{bin/spark-submit}} and re-directing the
stdout and stderr.
If stability is a concern, we can target this change towards the Hive 3.x
branch, which won't be released for a while. Migrating earlier will help us do
more testing of the {{SparkLauncher}} so we can report any bugs.
> Investigate SparkLauncher for HoS as alternative to bin/spark-submit
> --------------------------------------------------------------------
>
> Key: HIVE-16484
> URL: https://issues.apache.org/jira/browse/HIVE-16484
> Project: Hive
> Issue Type: Bug
> Components: Spark
> Reporter: Sahil Takiar
> Assignee: Sahil Takiar
> Attachments: HIVE-16484.1.patch
>
>
> The {{SparkClientImpl#startDriver}} currently looks for the {{SPARK_HOME}}
> directory and invokes the {{bin/spark-submit}} script, which spawns a
> separate process to run the Spark application.
> {{SparkLauncher}} was added in SPARK-4924 and is a programatic way to launch
> Spark applications.
> I see a few advantages:
> * No need to spawn a separate process to launch a HoS --> lower startup time
> * Simplifies the code in {{SparkClientImpl}} --> easier to debug
> * {{SparkLauncher#startApplication}} returns a {{SparkAppHandle}} which
> contains some useful utilities for querying the state of the Spark job
> ** It also allows the launcher to specify a list of job listeners
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
