[ https://issues.apache.org/jira/browse/HADOOP-12450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14962468#comment-14962468 ]
Hudson commented on HADOOP-12450: --------------------------------- FAILURE: Integrated in Hadoop-Hdfs-trunk #2446 (See [https://builds.apache.org/job/Hadoop-Hdfs-trunk/2446/]) HADOOP-12450. UserGroupInformation should not log at WARN level if no (stevel: rev e286512a7143427f2975ec92cdc4fad0a093a456) * hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/security/UserGroupInformation.java * hadoop-common-project/hadoop-common/CHANGES.txt > UserGroupInformation should not log at WARN level if no groups are found > ------------------------------------------------------------------------ > > Key: HADOOP-12450 > URL: https://issues.apache.org/jira/browse/HADOOP-12450 > Project: Hadoop Common > Issue Type: Improvement > Components: security > Reporter: Elliott Clark > Assignee: Elliott Clark > Priority: Minor > Fix For: 2.8.0 > > Attachments: HADOOP-12450-v1.patch, HADOOP-12450-v2.patch > > > HBase tries to get the groups of a user on every request. That user may or > may not exist on the box running Hadoop/HBase. > If that user doesn't exist currently Hadoop will log at the WARN level > everytime. This leads to gigs of log spam and serious GC issues. -- This message was sent by Atlassian JIRA (v6.3.4#6332)