You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Patrick Wendell (JIRA)" <ji...@apache.org> on 2014/09/26 01:50:38 UTC
[jira] [Resolved] (SPARK-3584) sbin/slaves doesn't work when we use
password authentication for SSH
[ https://issues.apache.org/jira/browse/SPARK-3584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Patrick Wendell resolved SPARK-3584.
------------------------------------
Resolution: Fixed
Fix Version/s: 1.2.0
Assignee: Kousuke Saruta
Target Version/s: 1.2.0 (was: 1.1.1, 1.2.0)
Resolved by:
https://github.com/apache/spark/pull/2444
> sbin/slaves doesn't work when we use password authentication for SSH
> --------------------------------------------------------------------
>
> Key: SPARK-3584
> URL: https://issues.apache.org/jira/browse/SPARK-3584
> Project: Spark
> Issue Type: Bug
> Components: Spark Core
> Affects Versions: 1.2.0
> Reporter: Kousuke Saruta
> Assignee: Kousuke Saruta
> Fix For: 1.2.0
>
>
> In sbin/slaves, ssh command run in the background but if we use password authentication, background ssh command doesn't work so sbin/slaves doesn't work.
> Also I suggest improvement for sbin/slaves.
> In current implementation, slaves file is trucked by Git but it can be edited by user so we prepare slaves.template instead of slaves.
> Default slaves file has one entry, localhost, so we should use localhost as a default host list.
> I modified sbin/slaves to choose localhost as a default host list.
--
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