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] Updated: (HDFS-800) The last block of a file under construction may change to the COMPLETE state in response to getAdditionalBlock or completeFileInternal
Date Fri, 15 Jan 2010 23:08:54 GMT

     [ https://issues.apache.org/jira/browse/HDFS-800?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Hairong Kuang updated HDFS-800:
-------------------------------

    Fix Version/s:     (was: 0.21.0)
       Issue Type: Improvement  (was: Bug)

Just want to make it clear. When I filed this jira, I thought it was a bug. But while I worked
on this, I realize that my proposed change is more like an optimization. Current trunk does
not do case 1. However if a block missed the state change in (1), the block's state will be
changed to be COMPLETE at a later time after a check if its replicas# meets the min replication
factor returns true.

> The last block of a file under construction may change to the COMPLETE state in response
to getAdditionalBlock or completeFileInternal
> --------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: HDFS-800
>                 URL: https://issues.apache.org/jira/browse/HDFS-800
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: name-node
>    Affects Versions: 0.21.0
>            Reporter: Hairong Kuang
>            Assignee: Hairong Kuang
>             Fix For: 0.22.0
>
>         Attachments: HDFS-800.patch
>
>
> Currently the last block changes to be the COMMITTED state. However, if the block already
has a valid finalizeded replica, it should be changed to be the COMPLETE state.

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


Mime
View raw message