Return-Path: X-Original-To: apmail-hadoop-common-user-archive@www.apache.org Delivered-To: apmail-hadoop-common-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id C7714D708 for ; Tue, 28 May 2013 11:48:12 +0000 (UTC) Received: (qmail 21036 invoked by uid 500); 28 May 2013 11:48:07 -0000 Delivered-To: apmail-hadoop-common-user-archive@hadoop.apache.org Received: (qmail 20555 invoked by uid 500); 28 May 2013 11:48:06 -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 20511 invoked by uid 99); 28 May 2013 11:48:04 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 28 May 2013 11:48:04 +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 (nike.apache.org: domain of samir.helpdoc@gmail.com designates 209.85.128.177 as permitted sender) Received: from [209.85.128.177] (HELO mail-ve0-f177.google.com) (209.85.128.177) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 28 May 2013 11:47:58 +0000 Received: by mail-ve0-f177.google.com with SMTP id cz10so1064327veb.22 for ; Tue, 28 May 2013 04:47:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=hQyD+2TKE5JmY+E+T1oRUL44DBwhIWHwfbK/z+jON90=; b=dxM+t454FKWgUPvWImfXI5Y6iUDnzoaXyBFlH4tUluPyEyRGU0UFkTIr7xG9Ts0qUK VC1XPbZxVESXlD1SkBBvuzR6uRc21gBcsIvSV+awYYP5RYS26A6ccn4LsiDJfl2POV/L fjw+KBrvAB57iGGjLR0KlIP2yVKI+H1TgM5bwiJc4MDy5S7Jd4Ra6/6TK31HyiAT/QZm rJhmqOiVsuHW/bwm80JT1JZCcw1ySFgKQJbhRcPqVv26bVPX5wpdLwtfiGDgepNBNE5W 7gvmj1KDzIGi2r2b3xGwepP+ib3E2nFfNXAy4rr7pkjhe6xz3SYbRjR3ZHbQBdaQ9LSQ fm1g== MIME-Version: 1.0 X-Received: by 10.52.163.207 with SMTP id yk15mr14764723vdb.42.1369741657767; Tue, 28 May 2013 04:47:37 -0700 (PDT) Received: by 10.59.10.230 with HTTP; Tue, 28 May 2013 04:47:37 -0700 (PDT) Date: Tue, 28 May 2013 17:17:37 +0530 Message-ID: Subject: Pulling data from secured hadoop cluster to another hadoop cluster From: samir das mohapatra To: cdh-user@cloudera.org, cdh-user@cloudera.com, user@hadoop.apache.org Content-Type: multipart/alternative; boundary=001a11c22ea2f205c504ddc5d4b4 X-Virus-Checked: Checked by ClamAV on apache.org --001a11c22ea2f205c504ddc5d4b4 Content-Type: text/plain; charset=ISO-8859-1 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. --001a11c22ea2f205c504ddc5d4b4 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hi All,
=A0 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 secur= ed hadoop box to another hadoop cluster , I could not able to ping=A0 name = node machine.=A0 In this approach how to run distcp command from target clu= ster 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.
--001a11c22ea2f205c504ddc5d4b4--