[
https://issues.apache.org/jira/browse/HADOOP-10442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13950607#comment-13950607
]
Hudson commented on HADOOP-10442:
---------------------------------
FAILURE: Integrated in Hadoop-Yarn-trunk #523 (See
[https://builds.apache.org/job/Hadoop-Yarn-trunk/523/])
HADOOP-10442. Group look-up can cause segmentation fault when certain JNI-based
mapping module is used. (Kihwal Lee via jeagles) (jeagles:
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1582451)
* /hadoop/common/trunk/hadoop-common-project/hadoop-common/CHANGES.txt
*
/hadoop/common/trunk/hadoop-common-project/hadoop-common/src/main/native/src/org/apache/hadoop/security/hadoop_user_info.c
> Group look-up can cause segmentation fault when certain JNI-based mapping
> module is used.
> -----------------------------------------------------------------------------------------
>
> Key: HADOOP-10442
> URL: https://issues.apache.org/jira/browse/HADOOP-10442
> Project: Hadoop Common
> Issue Type: Bug
> Affects Versions: 2.3.0, 2.4.0
> Reporter: Kihwal Lee
> Assignee: Kihwal Lee
> Priority: Blocker
> Fix For: 3.0.0, 2.4.0, 2.5.0
>
> Attachments: HADOOP-10442.patch
>
>
> When JniBasedUnixGroupsNetgroupMapping or JniBasedUnixGroupsMapping is used,
> we get segmentation fault very often. The same system ran 2.2 for months
> without any problem, but as soon as upgrading to 2.3, it started crashing.
> This resulted in multiple name node crashes per day.
> The server was running nslcd (nss-pam-ldapd-0.7.5-15.el6_3.2). We did not see
> this problem on the servers running sssd.
> There was one change in the C code and it modified the return code handling
> after getgrouplist() call. If the function returns 0 or a negative value less
> than -1, it will do realloc() instead of returning failure.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
