[
https://issues.apache.org/jira/browse/HADOOP-12450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14935600#comment-14935600
]
Steve Loughran commented on HADOOP-12450:
-----------------------------------------
# it should really be at debug; trace doesn't get used in the hadoop code.
# Given it's also swallowing the exception (which may be a sign of something
fundamental), maybe the logging should also include the nested exception.
What do others think?
> 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: Bug
> Reporter: Elliott Clark
> Assignee: Elliott Clark
> Attachments: HADOOP-12450-v1.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)
