[
https://issues.apache.org/jira/browse/HADOOP-6048?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12721606#action_12721606
]
Kan Zhang commented on HADOOP-6048:
-----------------------------------
attached a new patch, which bumps up the ClientDatanodeProtocol version to
signal the fact that now recoverBlock() never returns null and always returns a
newly generated access token as part of the return value. Also, reverted the
changes made in previous patches that changed the way how lastException is set
by sync() and createBlockOutputStream().
> Need to handle access token expiration when re-establishing the pipeline for
> dfs write
> --------------------------------------------------------------------------------------
>
> Key: HADOOP-6048
> URL: https://issues.apache.org/jira/browse/HADOOP-6048
> Project: Hadoop Core
> Issue Type: Bug
> Components: dfs, security
> Reporter: Kan Zhang
> Assignee: Kan Zhang
> Attachments: 6048-09.patch, 6048-11.patch, 6048-12.patch,
> 6048-14.patch, 6048-15.patch, 6048-16.patch, 6048-17.patch, 6048-18.patch
>
>
> Original access token may have expired when re-establishing the pipeline
> within processDatanodeError().
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
