hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hairong Kuang (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HDFS-592) Allow client to get a new generation stamp from NameNode
Date Mon, 14 Sep 2009 16:41:58 GMT

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

Hairong Kuang commented on HDFS-592:

> The initial pipeline setup for append should get its access token from the append() call
(like how it is done today). 

There is an undetermined delay from the time append is called to the time the initial pipeline
is set. A pipeline is set up when a client needs to send out the first packet. As we discussed
at the design time, an access token has to be fetched right before a pipeline is set up.

This behavior is parallel to what we do with file creation. When a client issues create, NN
does not return any access token. But before a pipeline is set up, the client calls addBlock
to get a new block and an access token. 

> Allow client to get a new generation stamp from NameNode
> --------------------------------------------------------
>                 Key: HDFS-592
>                 URL: https://issues.apache.org/jira/browse/HDFS-592
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>          Components: name-node
>    Affects Versions: Append Branch
>            Reporter: Hairong Kuang
>            Assignee: Hairong Kuang
>             Fix For: Append Branch
>         Attachments: newGS.patch, newGS1.patch
> This issue aims to  add an API to ClientProtocol that fetches a new generation stamp
and an access token from NameNode to support append or pipeline recovery.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message