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-565) Introduce block committing logic during new block allocation and file close.
Date Fri, 28 Aug 2009 04:58:59 GMT

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

Hairong Kuang commented on HDFS-565:

> This is useful when the client reopens the same file for append. I am not sure this was
relaxed, because it is only used in append now.
If the file is not closed, the client can not reopens the same file for append. We have one
writer semantics. I still do not understand why this is needed.

> Introduce block committing logic during new block allocation and file close.
> ----------------------------------------------------------------------------
>                 Key: HDFS-565
>                 URL: https://issues.apache.org/jira/browse/HDFS-565
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>          Components: hdfs client, name-node
>    Affects Versions: Append Branch
>            Reporter: Konstantin Shvachko
>            Assignee: Konstantin Shvachko
>             Fix For: Append Branch
>         Attachments: CommitBlock.patch, CommitBlock.patch
> {{ClientProtocol}} methods {{addBlock()}} and {{complete()}} need to include additional
parameter - a block, which has been successfully written to data-nodes. By sending this block
to the name-node the client confirms the generation stamp of the block and its length. The
block on the name-node changes its state to committed and will become complete as long as
one of the finalized replicas reported by data-nodes.

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

View raw message