You are viewing a plain text version of this content. The canonical link for it is here.

Posted to common-dev@hadoop.apache.org by "Kan Zhang (JIRA)" <ji...@apache.org> on 2009/06/17 06:42:07 UTC

[jira] Commented: (HADOOP-6048) Need to handle access token expiration when re-establishing the pipeline for dfs write

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

Kan Zhang commented on HADOOP-6048:
-----------------------------------

To be clear to the reader, the last patch removed null checking on the return value from recoverBlock() since it always returns a LocatedBlock object or throw an exception.

> 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
>
>
> 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.