[ https://issues.apache.org/jira/browse/HADOOP-7156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13004209#comment-13004209 ]
Eli Collins commented on HADOOP-7156: ------------------------------------- The approach and code look good to me. I would leave as is, no need to add autodetection, but we should document it in core-default so users are aware of the issue. I think leaving the workaround disabled for the tests is the right thing, this way it fails on a broken system which will help users identify that they need to enable the workaround. Also, the description seems appropriate to me, this isn't about POSIX compliance, it's just a bug in a library function, that will probably be fixed. > getpwuid_r is not thread-safe on RHEL6 > -------------------------------------- > > Key: HADOOP-7156 > URL: https://issues.apache.org/jira/browse/HADOOP-7156 > Project: Hadoop Common > Issue Type: Bug > Affects Versions: 0.22.0 > Environment: RHEL 6.0 "Santiago" > Reporter: Todd Lipcon > Assignee: Todd Lipcon > Priority: Critical > Fix For: 0.22.0 > > Attachments: hadoop-7156.txt, hadoop-7156.txt, hadoop-7156.txt > > > Due to the following bug in SSSD, functions like getpwuid_r are not > thread-safe in RHEL 6.0 if sssd is specified in /etc/nsswitch.conf (as it is > by default): > https://fedorahosted.org/sssd/ticket/640 > This causes many fetch failures in the case that the native libraries are > available, since the SecureIO functions call getpwuid_r as part of fstat. By > enabling -Xcheck:jni I get the following trace on JVM crash: > *** glibc detected *** /mnt/toolchain/JDK6u20-64bit/bin/java: free(): invalid > pointer: 0x0000003575741d23 *** > ======= Backtrace: ========= > /lib64/libc.so.6[0x3575675676] > /lib64/libnss_sss.so.2(_nss_sss_getpwuid_r+0x11b)[0x7fe716cb42cb] > /lib64/libc.so.6(getpwuid_r+0xdd)[0x35756a5dfd] -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira