hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Raju (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-3731) 2.0 release upgrade must handle blocks being written from 1.0
Date Mon, 30 Jul 2012 17:13:35 GMT

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

Raju commented on HDFS-3731:

In the upgrade process we usually rename the old folder to previous folder but here we have
2 folders (one contain finalised blocks and other in BBW) to handle ,I would like to propose

sd.root/previous >>> sd.root/current/BPID/current/finalized
sd.root/blocksbeingwritten >>> sd.root/current/BPID/current/rbw

NOTE: >>> hardlink
NOTE: blocksbeingwritten folder is not renamed since this can cause rollback problem with
old versions.

With the above fix there are some advantages
1. Simple change in existing code(2.X +) code,
2. No change required for old version code.(1.X -),
3. Rollback will work without any new effort,

Please correct me if I am wrong.
> 2.0 release upgrade must handle blocks being written from 1.0
> -------------------------------------------------------------
>                 Key: HDFS-3731
>                 URL: https://issues.apache.org/jira/browse/HDFS-3731
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: data-node
>    Affects Versions: 2.0.0-alpha
>            Reporter: Suresh Srinivas
>            Assignee: Todd Lipcon
>            Priority: Blocker
> Release 2.0 upgrades must handle blocks being written to (bbw) files from 1.0 release.
Problem reported by Brahma Reddy.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message