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 180AC10FB0 for ; Mon, 9 Sep 2013 20:48:34 +0000 (UTC) Received: (qmail 7471 invoked by uid 500); 9 Sep 2013 20:48:27 -0000 Delivered-To: apmail-hadoop-mapreduce-user-archive@hadoop.apache.org Received: (qmail 7376 invoked by uid 500); 9 Sep 2013 20:48:27 -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 7096 invoked by uid 99); 9 Sep 2013 20:48:27 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 09 Sep 2013 20:48:27 +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 amuise@hortonworks.com designates 74.125.82.54 as permitted sender) Received: from [74.125.82.54] (HELO mail-wg0-f54.google.com) (74.125.82.54) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 09 Sep 2013 20:48:20 +0000 Received: by mail-wg0-f54.google.com with SMTP id e11so4596273wgh.21 for ; Mon, 09 Sep 2013 13:48:00 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=JNeO1iz0G7OasuRzbwnyUdgDi3bfTqWMEg1Ng4LDTEY=; b=g0djXbshQs8vRqkh2JA2zd/lRDqQ+T16U6o9mXZLc5fv13dbO7JWEOhmJNS7d3q6iw eGltTwW24o7/zkGvxrqJWFDE/NOUozG5KA1oLfhN0Lwf8LJOCete4RTCk5PfcEbm8R9g 6ibMB5J+QGuYKLbknDNxrSQ/BkVKEBmvb8nL4rWAuCzY8qumV00qcXToQ2gQ3oUQitJW HIr86cUYmtqMMAReQWlNu9whVzLVPCVlp4oz0ym1lFIYOsbMzrf06WmmbUNLqXn95SrV +7Q29mksm6HVA9L3lBemfvUyL08J/2IrQj2t3FnWGz4WLFGmbUWIPMnEf1KrGYfySOKX zozQ== X-Gm-Message-State: ALoCoQm95HDkrRfrmowZ/u929/ttDFE4hVi9lb9mntsO6EhD4iFP7Z+5bR7Wpm2AVB7jRoetB73TVwNUPUuN/ia5TByhUXUkLKA1RPE8LFQrneh7f9JyPNI= MIME-Version: 1.0 X-Received: by 10.180.185.146 with SMTP id fc18mr10086719wic.44.1378759680674; Mon, 09 Sep 2013 13:48:00 -0700 (PDT) Received: by 10.216.139.71 with HTTP; Mon, 9 Sep 2013 13:48:00 -0700 (PDT) In-Reply-To: References: Date: Mon, 9 Sep 2013 16:48:00 -0400 Message-ID: Subject: Re: Hadoop on IPv6 From: Adam Muise To: user@hadoop.apache.org Content-Type: multipart/alternative; boundary=001a11c35472ff69d804e5f9807c X-Virus-Checked: Checked by ClamAV on apache.org --001a11c35472ff69d804e5f9807c Content-Type: text/plain; charset=US-ASCII I suggest you go to the mighty Google. This is not a Hadoop configuration question, it's a web server / proxy configuration. Starters: http://www.progob.nl/robmaaseu/index.php/an-easy-way-to-get-ipv6-ready-on-the-outside-ipv6-to-ipv4-proxy/ and proxying with nginx http://nginx.org/en/docs/http/ngx_http_proxy_module.html Eventually Knox will help out by adding a REST/Web set of gateways for Hadoop services: http://knox.incubator.apache.org For now, your web based gateway services on the cluster can be proxied and you can still land on your gateway box with ipv6 capabilities on the outside of the secure cluster. That gateway box would have direct ipv4 connections to the cluster services. Cheers, On Mon, Sep 9, 2013 at 4:35 PM, Aji Janis wrote: > Adam, > Thank you for the suggestion. Could you point me to any documentation that > can help with the configuration changes I need to make? Thanks. > > Aji > > > On Mon, Sep 9, 2013 at 1:30 PM, Adam Muise wrote: > >> Keep the Hadoop cluster and it's network backbone on IPv4. It should be >> isolated from the rest of your network for security and performance reasons >> already anyway. >> >> Enable IPv6 on your gateway nodes and let clients jump in for access via >> the ipv6 network and use the cluster via ipv4 on the gateway node. You >> could even setup a web proxy for some of the required sites using nginx or >> your favorite proxy server. Leave the ipv6 conversion of the Hadoop cluster >> until it is fully supported and well-tested. >> >> >> On Mon, Sep 9, 2013 at 1:19 PM, Aji Janis wrote: >> >>> We are moving to a IPv6 network. I know Hadoop installation says to >>> disable IPv6. Does anyone have any suggestions for work arround? Currently, >>> using Cloudera version 0.20.2-cdh3u5. Thanks in advance. >>> >> >> >> >> -- >> * >> * >> * >> * >> *Adam Muise* >> Solution Engineer >> *Hortonworks* >> amuise@hortonworks.com >> 416-417-4037 >> >> Hortonworks - Develops, Distributes and Supports Enterprise Apache Hadoop. >> >> Hortonworks Virtual Sandbox >> >> Hadoop: Disruptive Possibilities by Jeff Needham >> >> CONFIDENTIALITY NOTICE >> NOTICE: This message is intended for the use of the individual or entity >> to which it is addressed and may contain information that is confidential, >> privileged and exempt from disclosure under applicable law. If the reader >> of this message is not the intended recipient, you are hereby notified that >> any printing, copying, dissemination, distribution, disclosure or >> forwarding of this communication is strictly prohibited. If you have >> received this communication in error, please contact the sender immediately >> and delete it from your system. Thank You. > > > -- * * * * *Adam Muise* Solution Engineer *Hortonworks* amuise@hortonworks.com 416-417-4037 Hortonworks - Develops, Distributes and Supports Enterprise Apache Hadoop. Hortonworks Virtual Sandbox Hadoop: Disruptive Possibilities by Jeff Needham -- CONFIDENTIALITY NOTICE NOTICE: This message is intended for the use of the individual or entity to which it is addressed and may contain information that is confidential, privileged and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient, you are hereby notified that any printing, copying, dissemination, distribution, disclosure or forwarding of this communication is strictly prohibited. If you have received this communication in error, please contact the sender immediately and delete it from your system. Thank You. --001a11c35472ff69d804e5f9807c Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
I suggest you go to the mighty Google. This is not a Hadoo= p configuration question, it's a web server / proxy configuration.=A0
Starters:

and proxying with nginx=A0

Eventually Knox will help out by adding a REST/Web set= of gateways for Hadoop services:=A0
For now, your web based gateway services on the cluster can be proxied and = you can still land on your gateway box with ipv6 capabilities on the outsid= e of the secure cluster. That gateway box would have direct ipv4 connection= s to the cluster services.=A0

Cheers,


On Mon, Sep 9, 2013 at 4:35 PM, Aji J= anis <aji1705@gmail.com> wrote:
Adam,
Thank you for the= suggestion. Could you point me to any documentation that can help with the= configuration changes I need to make? Thanks.

Aji


On Mon, Sep 9, 20= 13 at 1:30 PM, Adam Muise <amuise@hortonworks.com> wrot= e:
Keep the Hadoop cluster and it's network backbone on I= Pv4. It should be isolated from the rest of your network for security and p= erformance reasons already anyway.=A0

Enable IPv6 on you= r gateway nodes and let clients jump in for access via the ipv6 network and= use the cluster via ipv4 on the gateway node. You could even setup a web p= roxy for some of the required sites using nginx or your favorite proxy serv= er. Leave the ipv6 conversion of the Hadoop cluster until it is fully suppo= rted and well-tested.=A0


On= Mon, Sep 9, 2013 at 1:19 PM, Aji Janis <aji1705@gmail.com> = wrote:
We are moving to a IPv6 = network. I know Hadoop installation says to disable IPv6. Does anyone have = any suggestions for work arround? Currently, using Cloudera version 0.20.2-= cdh3u5. Thanks in advance.



--

CONFIDENTIALITY NOTICE
NOTICE: This= message is intended for the use of the individual or entity to which it is= addressed and may contain information that is confidential, privileged and= exempt from disclosure under applicable law. If the reader of this message= is not the intended recipient, you are hereby notified that any printing, = copying, dissemination, distribution, disclosure or forwarding of this comm= unication is strictly prohibited. If you have received this communication i= n error, please contact the sender immediately and delete it from your syst= em. Thank You.




--

CONFIDENTIALITY NOTICE
NOTICE: This message is = intended for the use of the individual or entity to which it is addressed a= nd may contain information that is confidential, privileged and exempt from= disclosure under applicable law. If the reader of this message is not the = intended recipient, you are hereby notified that any printing, copying, dis= semination, distribution, disclosure or forwarding of this communication is= strictly prohibited. If you have received this communication in error, ple= ase contact the sender immediately and delete it from your system. Thank Yo= u. --001a11c35472ff69d804e5f9807c--