[
https://issues.apache.org/jira/browse/HDFS-4548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13593873#comment-13593873
]
Daryn Sharp commented on HDFS-4548:
-----------------------------------
BTW, earlier I filed HADOOP-9366 for the mutable hashCode. I think we probably
need a hashCode otherwise we can never use the token correctly in a collection.
I'm not sure I understand the data passthrough issue, would you elaborate?
This low level area is just handling the open of connections so higher level
callers can send the actual http operation. The retry policies must be able to
handle redoing the whole operation (including upload) or they are fundamentally
broken?
I realized these patches are incomplete. They only handle the case of actual
negotiation failing. If the token is acquired but expired, operations get a
401 response which I'm not handling...
> Webhdfs doesn't renegotiate SPNEGO token
> ----------------------------------------
>
> Key: HDFS-4548
> URL: https://issues.apache.org/jira/browse/HDFS-4548
> Project: Hadoop HDFS
> Issue Type: Bug
> Affects Versions: 2.0.0-alpha, 3.0.0, 0.23.7
> Reporter: Daryn Sharp
> Assignee: Daryn Sharp
> Priority: Critical
> Attachments: HDFS-4548.branch-23.patch, HDFS-4548.patch,
> HDFS-4548.patch
>
>
> When the webhdfs SPNEGO token expires, the fs doesn't attempt to renegotiate
> a new SPNEGO token. This renders webhdfs unusable for daemons that are
> logged in via a keytab which would allow a new SPNEGO token to be generated.
--
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
