[
https://issues.apache.org/jira/browse/SPARK-2960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14743415#comment-14743415
]
Danil Mironov commented on SPARK-2960:
--------------------------------------
The title of the issue is not that misleading, when one doesn't get
spark-something running after 'spark-something' was typed in, it's commonly
known as 'spark executables fail to start'. Following the symlinks does fix the
issue in hand.
Having executables {quote}configured by {{SPARK_HOME}} and/or
{{SPARK_CONF_DIR}} {quote} would be a nice solution, I'd vote for that.
This implies scripts treating those configurations as read-only and quitting
early and loudly if the latter is missing or crippled.
That's some rework though, not a bug to fix.
> Spark executables fail to start via symlinks
> --------------------------------------------
>
> Key: SPARK-2960
> URL: https://issues.apache.org/jira/browse/SPARK-2960
> Project: Spark
> Issue Type: Bug
> Components: Deploy
> Reporter: Shay Rojansky
> Priority: Minor
>
> The current scripts (e.g. pyspark) fail to run when they are executed via
> symlinks. A common Linux scenario would be to have Spark installed somewhere
> (e.g. /opt) and have a symlink to it in /usr/bin.
--
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
