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

dhruba borthakur updated HADOOP-2656:
-------------------------------------

    Attachment: upgradeGenStamp.patch

Incorporates most of Konstantin's comments. I left the definition of BlockTwo 
just because I think it is cleaner this way. Also, the reason some code is 
duplicated between BlockCrcUpgrade and BlockGenerationStampUpgrade is because 
the BlockCrcUpgrade code might probably go away in the next release or so.

> Support for upgrading existing cluster to facilitate appends to HDFS files
> --------------------------------------------------------------------------
>
>                 Key: HADOOP-2656
>                 URL: https://issues.apache.org/jira/browse/HADOOP-2656
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: dfs
>            Reporter: dhruba borthakur
>            Assignee: dhruba borthakur
>             Fix For: 0.18.0
>
>         Attachments: upgradeGenStamp.patch, upgradeGenStamp4.patch, 
> upgradeGenStamp5.patch
>
>
> HADOOP-1700 describes the design for supporting appends to HDFS files. This 
> design requires a distributed-upgrade to existing cluster installations. The 
> design specifies that the DataNode persist the 8-byte BlockGenerationStamp in 
> the block metadata file. The upgrade code will introduce this new field in 
> the block metadata file and initialize this value to 0.

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

Reply via email to