You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Andrew Or (JIRA)" <ji...@apache.org> on 2014/10/13 09:39:35 UTC
[jira] [Commented] (SPARK-3921) WorkerWatcher in Standalone mode
fail to come up due to invalid workerUrl
[ https://issues.apache.org/jira/browse/SPARK-3921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14169039#comment-14169039 ]
Andrew Or commented on SPARK-3921:
----------------------------------
https://github.com/apache/spark/pull/2779
> WorkerWatcher in Standalone mode fail to come up due to invalid workerUrl
> -------------------------------------------------------------------------
>
> Key: SPARK-3921
> URL: https://issues.apache.org/jira/browse/SPARK-3921
> Project: Spark
> Issue Type: Bug
> Affects Versions: 1.2.0
> Reporter: Aaron Davidson
> Assignee: Aaron Davidson
> Priority: Critical
>
> As of [this commit|https://github.com/apache/spark/commit/79e45c9323455a51f25ed9acd0edd8682b4bbb88#diff-79391110e9f26657e415aa169a004998R153], standalone mode appears to have lost its WorkerWatcher, because of the swapped workerUrl and appId parameters. We still put workerUrl before appId when we start standalone executors, and the Executor misinterprets the appId as the workerUrl and fails to create the WorkerWatcher.
> Note that this does not seem to crash the Standalone executor mode, despite the failing of the WorkerWatcher during its constructor.
--
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