hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Loughran (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-10315) Log the original exception when getGroups() fail in UGI.
Date Wed, 02 Sep 2015 10:57:46 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-10315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14727167#comment-14727167
] 

Steve Loughran commented on HADOOP-10315:
-----------------------------------------

Assuming this is just moving to {{log.warn(text,e)}}, 
do you want to supply a patch for this?

> Log the original exception when getGroups() fail in UGI.
> --------------------------------------------------------
>
>                 Key: HADOOP-10315
>                 URL: https://issues.apache.org/jira/browse/HADOOP-10315
>             Project: Hadoop Common
>          Issue Type: Bug
>    Affects Versions: 0.23.10, 2.2.0
>            Reporter: Kihwal Lee
>
> In UserGroupInformation, getGroupNames() swallows the original exception. There have
been many occasions that more information on the original exception could have helped.
> {code}
>   public synchronized String[] getGroupNames() {
>     ensureInitialized();
>     try {
>       List<String> result = groups.getGroups(getShortUserName());
>       return result.toArray(new String[result.size()]);
>     } catch (IOException ie) {
>       LOG.warn("No groups available for user " + getShortUserName());
>       return new String[0];
>     }
>   }
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message