Return-Path: X-Original-To: apmail-hadoop-user-archive@minotaur.apache.org Delivered-To: apmail-hadoop-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 7681AE2DC for ; Tue, 28 May 2013 14:28:29 +0000 (UTC) Received: (qmail 50859 invoked by uid 500); 28 May 2013 14:28:24 -0000 Delivered-To: apmail-hadoop-user-archive@hadoop.apache.org Received: (qmail 50584 invoked by uid 500); 28 May 2013 14:28:24 -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 50576 invoked by uid 99); 28 May 2013 14:28:24 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 28 May 2013 14:28:24 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of samir.helpdoc@gmail.com designates 209.85.212.52 as permitted sender) Received: from [209.85.212.52] (HELO mail-vb0-f52.google.com) (209.85.212.52) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 28 May 2013 14:28:19 +0000 Received: by mail-vb0-f52.google.com with SMTP id p12so4530043vbe.11 for ; Tue, 28 May 2013 07:27:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=jo28ZrCWIGQjmA2fu66ilbGr5m1XUvrN8Av4+YPCBoM=; b=xGclPBi0VpKMhHhrQsWiit69I/jYPFps0T+8QbbpPjlCaPjKVWkOPpKRTxp+FVzvT0 EzDISEx+trwzGYNzBxqu+ykcEbEIUd/v/Ts6PCaeKo99FyaqQx09qXGBmhjkbqQLIb+I bp81BcGFU80doZEVZIQF4Yrqn7Dpu6x4HW9Xs5Bb5kX6HaQ/Rhu95HbYh9bhxcSYyWIs rEiCI+qG8gnKyz37EYJBDTvfViHbHHGtxehqxJRkf1HSbOfUjn9tDzdSKjyLzig7RPu/ URnTxDVgIKnHxO2yuhZtQXolHCQ2DXyPG4UCjPj8+rdrdr/PGw4DGJtH6unyVToUwur3 WN9g== MIME-Version: 1.0 X-Received: by 10.52.94.204 with SMTP id de12mr6538966vdb.47.1369751278264; Tue, 28 May 2013 07:27:58 -0700 (PDT) Received: by 10.59.10.230 with HTTP; Tue, 28 May 2013 07:27:58 -0700 (PDT) In-Reply-To: References: Date: Tue, 28 May 2013 19:57:58 +0530 Message-ID: Subject: Re: Pulling data from secured hadoop cluster to another hadoop cluster From: samir das mohapatra To: user@hadoop.apache.org Content-Type: multipart/alternative; boundary=bcaec501651f5f28b904ddc8121e X-Virus-Checked: Checked by ClamAV on apache.org --bcaec501651f5f28b904ddc8121e Content-Type: text/plain; charset=ISO-8859-1 it is not hadoop security issue, the security is in host , I Mean to say in network level. I could not able to ping bcz source system is designed such a way that only you can connecto through ssh . If this is the case how to over come this problem. What extra parameter i need to add i ssh level so that i could able to ping the machine. All the servers are in same domain. On Tue, May 28, 2013 at 7:35 PM, Shahab Yunus wrote: > Also Samir, when you say 'secured', by any chance that cluster is secured > with Kerberos (rather than ssh)? > > -Shahab > > > On Tue, May 28, 2013 at 8:29 AM, Nitin Pawar wrote: > >> hadoop daemons do not use ssh to communicate. >> >> if your distcp job could not connect to remote server then either the >> connection was rejected by the target namenode or the it was not able to >> establish the network connection. >> >> were you able to see the hdfs on server1 from server2? >> >> >> On Tue, May 28, 2013 at 5:17 PM, samir das mohapatra < >> samir.helpdoc@gmail.com> wrote: >> >>> Hi All, >>> I could able to connect the hadoop (source ) cluster after ssh is >>> established. >>> >>> But i wanted to know, If I want to pull some data using distcp from >>> source secured hadoop box to another hadoop cluster , I could not able to >>> ping name node machine. In this approach how to run distcp command from >>> target cluster in with secured connection. >>> >>> Source: hadoop.server1 (ssh secured) >>> Target: hadoop.server2 (runing distcp here) >>> >>> >>> running command: >>> >>> distcp hftp://hadoop.server1:50070/dataSet >>> hdfs://hadoop.server2:54310/targetDataSet >>> >>> >>> Regards, >>> samir. >>> >> >> >> >> -- >> Nitin Pawar >> > > --bcaec501651f5f28b904ddc8121e Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
it is not hadoop security issue, the securi= ty is in host , I Mean to say in network level.

=A0I could not= able to ping bcz source system is designed such a way that only you can co= nnecto through ssh .
If this is the case how to over come this problem.

What = extra parameter i need to add i ssh level so that i could able to ping the = machine. All the servers are in same domain.




On Tue, May 28, 2013 at 7:35 PM, Shahab = Yunus <shahab.yunus@gmail.com> wrote:
Also Samir, when you say 'secured', by any chance = that cluster is secured with Kerberos (rather than ssh)?

-Shahab
=


=
On Tue, May 28, 2013 at 8:29 AM, Nitin Pawar <nitinpawar432@gmail.c= om> wrote:
hadoop daemons do not use ssh to communicate.=A0

<= /div>
if =A0your distcp job could not connect to remote server then eit= her the connection was rejected by the target namenode or the it was not ab= le to establish the network connection.=A0

were you able to see the hdfs on server1 from server2?= =A0


On Tue, May 28, 2013 at 5:17 PM, samir das mohapatra <s= amir.helpdoc@gmail.com> wrote:
Hi All,
= =A0 I could able to connect the hadoop (source ) cluster after ssh is estab= lished.

But i wanted to know, If I want to pull some data using dist= cp from source secured hadoop box to another hadoop cluster , I could not a= ble to ping=A0 name node machine.=A0 In this approach how to run distcp com= mand from target cluster in with secured connection.

Source: hadoop.server1 (ssh secured)
Target:= =A0 hadoop.server2 (runing distcp here)


running comma= nd:

distcp hftp://hadoop.server1:50070/dataSet=A0=A0=A0 hdfs://hadoo= p.server2:54310/targetDataSet


Regards,
samir.



<= font color=3D"#888888">--
Nitin Pawar


--bcaec501651f5f28b904ddc8121e--