Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 1D7B0200B3B for ; Mon, 11 Jul 2016 15:33:57 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 1BF80160A78; Mon, 11 Jul 2016 13:33:57 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 3CD55160A5E for ; Mon, 11 Jul 2016 15:33:56 +0200 (CEST) Received: (qmail 89243 invoked by uid 500); 11 Jul 2016 13:33:54 -0000 Mailing-List: contact user-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list user@hadoop.apache.org Received: (qmail 89230 invoked by uid 99); 11 Jul 2016 13:33:53 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 11 Jul 2016 13:33:53 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 749F9C249A for ; Mon, 11 Jul 2016 13:33:53 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.179 X-Spam-Level: * X-Spam-Status: No, score=1.179 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=2, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd1-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx2-lw-us.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id Ay3Le79UUleh for ; Mon, 11 Jul 2016 13:33:51 +0000 (UTC) Received: from mail-wm0-f53.google.com (mail-wm0-f53.google.com [74.125.82.53]) by mx2-lw-us.apache.org (ASF Mail Server at mx2-lw-us.apache.org) with ESMTPS id 8A4365F2C5 for ; Mon, 11 Jul 2016 13:33:50 +0000 (UTC) Received: by mail-wm0-f53.google.com with SMTP id f126so90783865wma.1 for ; Mon, 11 Jul 2016 06:33:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to; bh=0Qosxyoi4IRSt8Wt9RbQ81q6vEg0AJ42y4RT14hHKqo=; b=HZVnewhH9VM47NMQ7eGQgZWghrcJ0bxCAi7cI3OoXJRxvXiNcm5jsNVNbDdHhauGUJ nU5pDzH/8DVrWf6R6wB4RQNYi7J0jtLPTWDwOMYWiAFWqkwUd3rzF53rEf6Cup4Jttuf i1p6VGD12gX701C6Otdjcros/sFN9KPEeTMh5QLrpoSczCTJLFp4mF/O3w6qxiDFnPjr +FZ8hb1L3LYvuBDkM/o4fbNSGJJi+oOPyWMzFJi6RF7IuhLnXykqUQYlQ7oLUfMDkyVL ITpcB+iNZQdoa0b7oo4AHcRZswMYHP9b17u9xpKy9rDhhfIyOKugIVTYJror6I1UZBhB wRaQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=0Qosxyoi4IRSt8Wt9RbQ81q6vEg0AJ42y4RT14hHKqo=; b=EvQMZYeGSq4W5FXwbKOGhsVO8K/QPjss8/jiohWKhevR8MOF1D2yiW4Oatjn0yilrT tLdrfGEAqkLRUuM1xYQZyBIDeG3smpQwm5xQSHJ2CT9Wpgc2DrqXka6Sn1v5O0h8QQI/ UkbrVsFotBdSGGk4uf+JrkMJsIIFZQkBf2R9oXfh7qACIVFgrk4VC/PGmcoHzVq3xqYs /Aei6GaNj/+4gwoTNtWVNSNaWXpv0cWPz7JlFx1OcDt7stha8lwfv/3C9J4IZlDo4wsP ZB3GTeivrlrRUT00tP89ksVfRpWuSAf0nVloJTGgJlGPIsrwF9Q+A9VBRYs2Wd9t/Rwe 2veA== X-Gm-Message-State: ALyK8tIpIH5AkVCt6zEeKy7qoA5BWntj2wxtVV+aoz2uug87VZYBibuGkxZ9fsicScagw3kUduRgB4i6b97Ptg== X-Received: by 10.28.154.21 with SMTP id c21mr12635579wme.63.1468244028867; Mon, 11 Jul 2016 06:33:48 -0700 (PDT) MIME-Version: 1.0 Received: by 10.28.157.81 with HTTP; Mon, 11 Jul 2016 06:33:48 -0700 (PDT) From: Jochen Hebbrecht Date: Mon, 11 Jul 2016 15:33:48 +0200 Message-ID: Subject: Windows Hadoop client timeout exception connecting to Linux Hadoop cluster To: user@hadoop.apache.org Content-Type: multipart/alternative; boundary=001a114bde2cc8cda005375c333f archived-at: Mon, 11 Jul 2016 13:33:57 -0000 --001a114bde2cc8cda005375c333f Content-Type: text/plain; charset=UTF-8 Hi, This is the situation: a Hadoop cluster running on a Linux environment (version 2.5.0 CDH 5.3.3). We can contact the cluster on a Linux client with no issues and perform jobs on it. {bash} $ hadoop --config ../etc/myenvironment fs -ls / {bash} => is working fine On a Windows machine, we use exactly the same configuration and client, but the connection to the server takes a very longs time and eventually gets killed. {bash} $ hadoop --config ../etc/myenvironment/ fs -ls / Java config name: null Native config name: C:\WINDOWS\krb5.ini 2016-07-11 15:25:21,138 INFO [main] ipc.Client (Client.java:handleConnectionTimeout(814)) - Retrying connect to server: XXX:8020. Already tried 0 time(s); maxRetries=45 2016-07-11 15:25:41,138 INFO [main] ipc.Client (Client.java:handleConnectionTimeout(814)) - Retrying connect to server: XXX:8020. Already tried 1 time(s); maxRetries=45 2016-07-11 15:26:01,156 INFO [main] ipc.Client (Client.java:handleConnectionTimeout(814)) - Retrying connect to server: XXX:8020. Already tried 2 time(s); maxRetries=45 ... {bash} I think I'm running into this issue: https://discuss.zendesk.com/hc/en-us/articles/203758976-hdfs-dfs-ls-commands-will-hang-indefinitely-when-secure-hdfs-is-enabled Although my principal looks OK: {bash} $ klist Ticket cache: FILE:/tmp/krb5cc_1291429 Default principal: myusername@mydomain Valid starting Expires Service principal 07/11/2016 15:03:00 07/12/2016 01:03:00 krbtgt/mydomain@mydomainname renew until 07/11/2016 15:03:00 {bash} Any idea how I can debug this? Kind regards, Jochen Hebbrecht --001a114bde2cc8cda005375c333f Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi,

This is the situation: a Hadoop clu= ster running on a Linux environment (version=C2=A02.5.0 CDH 5.3.3). We can = contact the cluster on a Linux client with no issues and perform jobs on it= .

{bash}
$ hadoop --config ../etc/myenvi= ronment fs -ls /
{bash}
=3D> is working fine

On a Windows machine, we use exactly the same configu= ration and client, but the connection to the server takes a very longs time= and eventually gets killed.

{bash}
=
$ hadoop --config ../etc/myenvironment/ fs -ls /
Java config= name: null
Native config name: C:\WINDOWS\krb5.ini
201= 6-07-11 15:25:21,138 INFO =C2=A0[main] ipc.Client (Client.java:handleConnec= tionTimeout(814)) - Retrying connect to server: XXX:8020. Already tried 0 t= ime(s); maxRetries=3D45
2016-07-11 15:25:41,138 INFO =C2=A0[main]= ipc.Client (Client.java:handleConnectionTimeout(814)) - Retrying connect t= o server: XXX:8020. Already tried 1 time(s); maxRetries=3D45
2016= -07-11 15:26:01,156 INFO =C2=A0[main] ipc.Client (Client.java:handleConnect= ionTimeout(814)) - Retrying connect to server: XXX:8020. Already tried 2 ti= me(s); maxRetries=3D45
...
{bash}
<= br>
Although my principal looks OK:

{bash}
$ klist
Ticket = cache: FILE:/tmp/krb5cc_1291429
Default principal: myusername@myd= omain

Valid starting =C2=A0 =C2=A0 =C2=A0 Expires = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Service principal
07/11/2016 15:03:00 =C2=A007/12/2016 01:03:00 =C2=A0krbtgt/mydomain@mydoma= inname
=C2=A0 =C2=A0 =C2=A0 =C2=A0 renew until 07/11/2016 15:03:0= 0
{bash}

Any idea how I can de= bug this?

Kind regards,
Jochen Hebbrecht=

--001a114bde2cc8cda005375c333f--