[
https://issues.apache.org/jira/browse/HADOOP-10442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Nauroth updated HADOOP-10442:
-----------------------------------
Hadoop Flags: Reviewed
+1 for the patch. Thank you, Kihwal.
bq. -1 tests included. The patch doesn't appear to include any new or modified
tests.
This is not something easily covered with an automated test. Have you been
able to verify the patch manually in one your clusters that had the segfaults?
> 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
> 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)
