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

Yu Gao commented on HDFS-3676:
------------------------------

Do we have any update on this issue? The TGT auto-renewal doesn't work for 
libhdfs, which is a big limitation for applications using this c interface.
                
> handleSaslConnection failure doesn't try to renew the correct UGI
> -----------------------------------------------------------------
>
>                 Key: HDFS-3676
>                 URL: https://issues.apache.org/jira/browse/HDFS-3676
>             Project: Hadoop HDFS
>          Issue Type: Bug
>    Affects Versions: 2.0.0-alpha
>            Reporter: Colin Patrick McCabe
>            Assignee: Colin Patrick McCabe
>
> Client.java has this code:
> {code}
>     private synchronized void handleSaslConnectionFailure(
>         final int currRetries, final int maxRetries, final Exception ex,
>         final Random rand, final UserGroupInformation ugi) throws IOException,
>         InterruptedException {
>       ugi.doAs(new PrivilegedExceptionAction<Object>() {
>         public Object run() throws IOException, InterruptedException {
>           final short MAX_BACKOFF = 5000;
>           closeConnection();
>           disposeSasl();
>           if (shouldAuthenticateOverKrb()) {
>             if (currRetries < maxRetries) {
>               if(LOG.isDebugEnabled()) {
>                 LOG.debug("Exception encountered while connecting to "
>                     + "the server : " + ex);
>               }
>               // try re-login
>               if (UserGroupInformation.isLoginKeytabBased()) {
>                 UserGroupInformation.getLoginUser().reloginFromKeytab();
>               } else {
>                 UserGroupInformation.getLoginUser().reloginFromTicketCache();
>               }
> {code}
> It's not renewing the UGI that had the problem, it's renewing the loginUser.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to