Return-Path: 
 <user-return-18773-apmail-hadoop-hdfs-user-archive=hadoop.apache.org@hadoop.apache.org>
X-Original-To: apmail-hadoop-hdfs-user-archive@minotaur.apache.org
Delivered-To: apmail-hadoop-hdfs-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 1E3901080A
	for <apmail-hadoop-hdfs-user-archive@minotaur.apache.org>;
 Mon, 23 Feb 2015 15:49:44 +0000 (UTC)
Received: (qmail 18280 invoked by uid 500); 23 Feb 2015 15:49:38 -0000
Delivered-To: apmail-hadoop-hdfs-user-archive@hadoop.apache.org
Received: (qmail 18155 invoked by uid 500); 23 Feb 2015 15:49:38 -0000
Mailing-List: contact user-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:user-help@hadoop.apache.org>
List-Unsubscribe: <mailto:user-unsubscribe@hadoop.apache.org>
List-Post: <mailto:user@hadoop.apache.org>
List-Id: <user.hadoop.apache.org>
Reply-To: user@hadoop.apache.org
Delivered-To: mailing list user@hadoop.apache.org
Received: (qmail 18139 invoked by uid 99); 23 Feb 2015 15:49:38 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 23 Feb 2015 15:49:38 +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 ajohnson@etsy.com designates
 74.125.82.171 as permitted sender)
Received: from [74.125.82.171] (HELO mail-we0-f171.google.com) (74.125.82.171)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 23 Feb 2015 15:49:34 +0000
Received: by wesx3 with SMTP id x3so19308670wes.7
        for <user@hadoop.apache.org>; Mon, 23 Feb 2015 07:48:28 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=etsy.com; s=google;
        h=mime-version:date:message-id:subject:from:to:content-type;
        bh=gIJg3jFCerUnxjTyI5oAmLo/sn+Nf77+15gHjqFkups=;
        b=hhDPjAlPiBHsmi4cVRNVDG2zdlkEFIyEK4jj9xOxUZvy4yq8Z3LzrxL7f0eDGcQSOI
         M3DoYEz+tCntF/UwCGIsoVDrsucgnyBKg8lT7VxIoKxOfsCiYbdNc/Of4R+UBmrwI/bd
         ggogOQ0aIM1WMx3dGErYiII3sHhmNX0iYMcCE=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20130820;
        h=x-gm-message-state:mime-version:date:message-id:subject:from:to
         :content-type;
        bh=gIJg3jFCerUnxjTyI5oAmLo/sn+Nf77+15gHjqFkups=;
        b=gQJS1g8KQFBId6XfpX1Z9o1g6idL0ftdt1EEl33cc79A9YEhqUUnGGd2gOQtteQ+m2
         8uqHiJN1clbG4aZ70IAz90R+HzgnOFZF6CdoDCasln2aMajTqjH3ON7iJDc2lgeJQ+Tb
         I1vDi9rkVL0WLLN5aqAjsEKLk7n+vi4yKFO0dyc9AE5ccy7wLguoa5fKUklsF0OelHIP
         b3yqnsRESshcJd6jLJBwr/hFQH5yJQLIDIUsbPWLD2SAxdOrI1grH0Rx6l8pJJbVvB06
         Lg/BH7Yj1E6tf2wnfoNgHhCb8wK1R69UHyTvrzSNHw9031PJf4wTgZ0wWx/7fmr9eR5o
         n+UQ==
X-Gm-Message-State: 
 ALoCoQnHOFUvk0Fig6vYvDHZFe7A1sVpDofuPrM9M5IlbmFbeT2OC6sGY2UOy8dEURQWZAfdc/ts
MIME-Version: 1.0
X-Received: by 10.180.198.101 with SMTP id jb5mr21228616wic.92.1424706508031;
 Mon, 23 Feb 2015 07:48:28 -0800 (PST)
Received: by 10.28.178.9 with HTTP; Mon, 23 Feb 2015 07:48:27 -0800 (PST)
Date: Mon, 23 Feb 2015 10:48:27 -0500
Message-ID: 
 <CAOGNzBmDRGngOa0+aFrhcXPMPzhWx00oP2v2P_f=RrghgF6Uiw@mail.gmail.com>
Subject: Hadoop and nslcd
From: Andrew Johnson <ajohnson@etsy.com>
To: user@hadoop.apache.org
Content-Type: multipart/alternative; boundary=047d7b624d14522437050fc35595
X-Virus-Checked: Checked by ClamAV on apache.org

--047d7b624d14522437050fc35595
Content-Type: text/plain; charset=UTF-8

Hey everyone,

I am seeing an intermittent issue with the Namenode looking up the groups
for a given user.  We are using JniBasedUnixGroupsMapping.

I see messages like the following in the namenode logs:

015-02-23 15:42:37,184 WARN
org.apache.hadoop.security.UserGroupInformation: No groups available for
user <username>

The affected users do exist and are in groups.  The failures occur when
looking up groups from LDAP.  It is not consistent either - sometimes the
group lookups succeed and sometimes they do not.  When the lookup fails, I
see the following in /var/log/messages:

Feb 23 15:37:52 nn01 nslcd[21501]: [37e80a] error reading from client:
Success

I started seeing this with nslcd 0.7.5, but have upgraded to 0.8.12 and
have the same issue.  I've also tried increasing the number of threads for
nslcd, but that also did not help.

Has anyone had similar issues?

Thanks for your help!

-- 
Andrew Johnson

--047d7b624d14522437050fc35595
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Hey everyone,</div><div><br></div><div>I am seeing an=
 intermittent issue with the Namenode looking up the groups for a given use=
r.=C2=A0 We are using=C2=A0JniBasedUnixGroupsMapping.</div><div><br></div><=
div>I see messages like the following in the namenode logs:</div><div><br><=
/div><div><font face=3D"monospace, monospace">015-02-23 15:42:37,184 WARN o=
rg.apache.hadoop.security.UserGroupInformation: No groups available for use=
r &lt;username&gt;</font><br></div><div><br></div><div>The affected users d=
o exist and are in groups.=C2=A0 The failures occur when looking up groups =
from LDAP.=C2=A0 It is not consistent either - sometimes the group lookups =
succeed and sometimes they do not.=C2=A0 When the lookup fails, I see the f=
ollowing in /var/log/messages:</div><div><br></div><div><font face=3D"monos=
pace, monospace">Feb 23 15:37:52 nn01 nslcd[21501]: [37e80a] error reading =
from client: Success<br></font></div><div><br></div><div>I started seeing t=
his with nslcd 0.7.5, but have upgraded to 0.8.12 and have the same issue.=
=C2=A0 I&#39;ve also tried increasing the number of threads for nslcd, but =
that also did not help.</div><div><br></div><div>Has anyone had similar iss=
ues?</div><div><br></div><div>Thanks for your help!</div><div><br></div>-- =
<br><div class=3D"gmail_signature"><div dir=3D"ltr">Andrew Johnson</div></d=
iv>
</div>

--047d7b624d14522437050fc35595--