You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Punya Biswal (JIRA)" <ji...@apache.org> on 2015/04/16 01:53:59 UTC
[jira] [Updated] (SPARK-6952) spark-daemon.sh PID reuse check fails
on long classpath
[ https://issues.apache.org/jira/browse/SPARK-6952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Punya Biswal updated SPARK-6952:
--------------------------------
Summary: spark-daemon.sh PID reuse check fails on long classpath (was: spark-daemon.sh fails on long classpath)
> spark-daemon.sh PID reuse check fails on long classpath
> -------------------------------------------------------
>
> Key: SPARK-6952
> URL: https://issues.apache.org/jira/browse/SPARK-6952
> Project: Spark
> Issue Type: Bug
> Components: Deploy
> Affects Versions: 1.3.0
> Reporter: Punya Biswal
>
> {{sbin/spark-daemon.sh}} uses {{ps -p "$TARGET_PID" -o args=}} to figure out whether the process running with the expected PID is actually a Spark daemon. When running with a large classpath, the output of {{ps}} gets truncated and the check fails spuriously.
> I think we should weaken the check to see if it's a java command (which is something we do in other parts of the script) rather than looking for the specific main class name. This means that SPARK-4832 might happen under a slightly broader range of circumstances (a *java* program happened to reuse the same PID), but it seems worthwhile compared to failing consistently with a large classpath.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org