hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Colin Patrick McCabe (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HDFS-3731) 2.0 release upgrade must handle blocks being written from 1.0
Date Tue, 14 Aug 2012 19:43:38 GMT

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

Colin Patrick McCabe updated HDFS-3731:
---------------------------------------

    Description: 
Release 2.0 upgrades must handle blocks being written to (bbw) files from 1.0 release. Problem
reported by Brahma Reddy.

The {{DataNode}} will only have one block pool after upgrading from a 1.x release.  (This
is because in the 1.x releases, there were no block pools-- or equivalently, everything was
in the same block pool).  During the upgrade, we should hardlink the block files from the
{{blocksBeingWritten}} directory into the {{rbw}} directory of this block pool.  Similarly,
on {{-finalize}}, we should delete the {{blocksBeingWritten}} directory.

  was:
Release 2.0 upgrades must handle blocks being written to (bbw) files from 1.0 release. Problem
reported by Brahma Reddy.


    
> 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: Colin Patrick McCabe
>            Priority: Blocker
>         Attachments: HDFS-3731.002.patch, HDFS-3731.003.patch
>
>
> Release 2.0 upgrades must handle blocks being written to (bbw) files from 1.0 release.
Problem reported by Brahma Reddy.
> The {{DataNode}} will only have one block pool after upgrading from a 1.x release.  (This
is because in the 1.x releases, there were no block pools-- or equivalently, everything was
in the same block pool).  During the upgrade, we should hardlink the block files from the
{{blocksBeingWritten}} directory into the {{rbw}} directory of this block pool.  Similarly,
on {{-finalize}}, we should delete the {{blocksBeingWritten}} directory.

--
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

        

Mime
View raw message