Return-Path: X-Original-To: apmail-hadoop-mapreduce-user-archive@minotaur.apache.org Delivered-To: apmail-hadoop-mapreduce-user-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id AA2A5E9A3 for ; Tue, 5 Feb 2013 23:06:48 +0000 (UTC) Received: (qmail 96895 invoked by uid 500); 5 Feb 2013 23:06:43 -0000 Delivered-To: apmail-hadoop-mapreduce-user-archive@hadoop.apache.org Received: (qmail 96807 invoked by uid 500); 5 Feb 2013 23:06:43 -0000 Mailing-List: contact user-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@hadoop.apache.org Delivered-To: mailing list user@hadoop.apache.org Received: (qmail 96798 invoked by uid 99); 5 Feb 2013 23:06:43 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 05 Feb 2013 23:06:43 +0000 X-ASF-Spam-Status: No, hits=1.7 required=5.0 tests=FREEMAIL_ENVFROM_END_DIGIT,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of jayunit100@gmail.com designates 209.85.217.177 as permitted sender) Received: from [209.85.217.177] (HELO mail-lb0-f177.google.com) (209.85.217.177) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 05 Feb 2013 23:06:37 +0000 Received: by mail-lb0-f177.google.com with SMTP id go11so675376lbb.22 for ; Tue, 05 Feb 2013 15:06:16 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=JeyjxjzhZmX/i9lyMpqDQoFacyS1OSCI7HJhJeLcyPc=; b=ciwl0K0+MomMTmrXwkJsio10/ztSw/m3KSRP7HW/ThCz393lnoPrjLx5j2+09eJgmV 57Erjgx8d8QfDrgEfORq+SOzokgukwf7Yxu8UEdECCQXO4kZp6qcTYe7ILdhmZKk3xzm 55n/p0ZVsVeJaVKkjF0DQPvDJMK8rTwP18Pkd3lb6Dej5dvVUwvvojiUjxzLt2cCH8UJ IXeczu95UMPQYoTcj1NjvLDGwdMg4crGh7J5vubaVoXRX1eVbHNa/YkKV4v0n8f0CMvD V6s4fIBrfMr3nwmQVIhnCNXnWP9pUW/RAt0/nCAzQe0A9SfxZrcwPPXjx6yddi8Pu9KG wE+w== MIME-Version: 1.0 X-Received: by 10.152.133.133 with SMTP id pc5mr24549723lab.32.1360105565293; Tue, 05 Feb 2013 15:06:05 -0800 (PST) Received: by 10.112.30.101 with HTTP; Tue, 5 Feb 2013 15:06:05 -0800 (PST) Date: Tue, 5 Feb 2013 18:06:05 -0500 Message-ID: Subject: Specific HDFS tasks where is passwordless SSH is necessary From: Jay Vyas To: "common-user@hadoop.apache.org" Content-Type: multipart/alternative; boundary=f46d042ef753138b4304d50241e4 X-Virus-Checked: Checked by ClamAV on apache.org --f46d042ef753138b4304d50241e4 Content-Type: text/plain; charset=ISO-8859-1 When setting up passwordless ssh on a cluster, its clear that the namenode needs to be able to ssh into task trackers to start/stop nodes and restart the cluster. What else is passwordless SSH used for? Do TaskTrackers/DataNodes ever SSH into each other horizontally ? Or is SSH only used for one-way nn to tt operations? -- Jay Vyas http://jayunit100.blogspot.com --f46d042ef753138b4304d50241e4 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
When setting up passwordless ssh on a cluster, its cl= ear that the namenode needs to be able to ssh into task trackers to start/s= top nodes and restart the cluster.

What else is passwordless S= SH used for?=A0 Do TaskTrackers/DataNodes ever SSH into each other horizont= ally ? Or is SSH only used for one-way nn to tt operations?
--f46d042ef753138b4304d50241e4--