Return-Path: Delivered-To: apmail-hadoop-core-user-archive@www.apache.org Received: (qmail 73702 invoked from network); 21 Jan 2009 12:27:55 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 21 Jan 2009 12:27:55 -0000 Received: (qmail 78490 invoked by uid 500); 21 Jan 2009 12:27:50 -0000 Delivered-To: apmail-hadoop-core-user-archive@hadoop.apache.org Received: (qmail 78092 invoked by uid 500); 21 Jan 2009 12:27:49 -0000 Mailing-List: contact core-user-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: core-user@hadoop.apache.org Delivered-To: mailing list core-user@hadoop.apache.org Received: (qmail 78081 invoked by uid 99); 21 Jan 2009 12:27:49 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 21 Jan 2009 04:27:49 -0800 X-ASF-Spam-Status: No, hits=0.2 required=10.0 tests=SPF_PASS,URIBL_GREY X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of amitsaha.in@gmail.com designates 64.233.170.191 as permitted sender) Received: from [64.233.170.191] (HELO rn-out-0910.google.com) (64.233.170.191) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 21 Jan 2009 12:27:40 +0000 Received: by rn-out-0910.google.com with SMTP id k32so336567rnd.12 for ; Wed, 21 Jan 2009 04:27:19 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=LdS6+95hi/6u8eETL50ZX+n4TjQHPHnjAjO4E/J9uIE=; b=VsCTh2tghJKSxn1GsdXbwt9WL40A2R28R2ZL3VLGHRMUL8xIJl3GqO05VUwfGnlnP0 vDyY5EhmwWIRHOdiJdZa4krBIt+8KHzOK4G10xYire+pNIprw8k8QJNxYW64lQ7zuoQD DCNNgXQuVNi9HG2gCNBb+1CV6MDYbPPeQTDrA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=nIk6XEYjf/cjuvc440Z7Xy41YGRfEjAwezh293b1BN2/z6dGCiud9v/8FoGP31z5+O txHYcajNi7EojobOLNj6CeLwWmEwSD9VvlN5dkDfvrGiE2tpq4sIz8kS+QMIj9bWUXpp SrkRJLtUbGBQaV2oUfSE1N0fx5ShTJMwM1FaA= MIME-Version: 1.0 Received: by 10.150.197.8 with SMTP id u8mr4112726ybf.22.1232540839728; Wed, 21 Jan 2009 04:27:19 -0800 (PST) In-Reply-To: <8EA6555451F4C44E8AD50B576801F28DE958A7@WEBEXCHANGE02.webde.local> References: <8EA6555451F4C44E8AD50B576801F28DE958A7@WEBEXCHANGE02.webde.local> Date: Wed, 21 Jan 2009 17:57:19 +0530 Message-ID: <547db2260901210427r5bef38es1b206524f677c90e@mail.gmail.com> Subject: Re: Why does Hadoop need ssh access to master and slaves? From: "Amit k. Saha" To: core-user@hadoop.apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org On Wed, Jan 21, 2009 at 5:53 PM, Matthias Scherer wrote: > Hi all, > > we've made our first steps in evaluating hadoop. The setup of 2 VMs as a > hadoop grid was very easy and works fine. > > Now our operations team wonders why hadoop has to be able to connect to > the master and slaves via password-less ssh?! Can anyone give us an > answer to this question? 1. There has to be a way to connect to the remote hosts- slaves and a secondary master, and SSH is the secure way to do it 2. It has to be password-less to enable automatic logins -Amit > > Thanks & Regards > Matthias > -- Amit Kumar Saha http://amitksaha.blogspot.com http://amitsaha.in.googlepages.com/ *Bangalore Open Java Users Group*:http:www.bojug.in