[
https://issues.apache.org/jira/browse/HADOOP-10442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13948350#comment-13948350
]
Kihwal Lee commented on HADOOP-10442:
-------------------------------------
The return code handling was modified in HADOOP-10087. This is the only change
in the JNI user-group mapping modules between 2.2 and 2.3.
> 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
> Priority: Blocker
>
> 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)
