[ 
https://issues.apache.org/jira/browse/HDFS-15545?focusedWorklogId=475943&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-475943
 ]

ASF GitHub Bot logged work on HDFS-15545:
-----------------------------------------

                Author: ASF GitHub Bot
            Created on: 28/Aug/20 18:38
            Start Date: 28/Aug/20 18:38
    Worklog Time Spent: 10m 
      Work Description: ibuenros commented on pull request #2255:
URL: https://github.com/apache/hadoop/pull/2255#issuecomment-683062619


   The test failures seem to all be on the server-side of HDFS. No changes in 
this PR are on server side, so they should be unrelated.


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


Issue Time Tracking
-------------------

    Worklog Id:     (was: 475943)
    Time Spent: 40m  (was: 0.5h)

> (S)Webhdfs will not use updated delegation tokens available in the ugi after 
> the old ones expire
> ------------------------------------------------------------------------------------------------
>
>                 Key: HDFS-15545
>                 URL: https://issues.apache.org/jira/browse/HDFS-15545
>             Project: Hadoop HDFS
>          Issue Type: Bug
>            Reporter: Issac Buenrostro
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 40m
>  Remaining Estimate: 0h
>
> WebHdfsFileSystem can select a delegation token to use from the current user 
> UGI. The token selection is sticky, and WebHdfsFileSystem will re-use it 
> every time without searching the UGI again.
> If the previous token expires, WebHdfsFileSystem will catch the exception and 
> attempt to get a new token. However, the mechanism to get a new token 
> bypasses searching for one on the UGI, so even if there is external logic 
> that has retrieved a new token, it is not possible to make the FileSystem use 
> the new, valid token, rendering the FileSystem object unusable.
> A simple fix would allow WebHdfsFileSystem to re-search the UGI, and if it 
> finds a different token than the cached one try to use it.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org

Reply via email to