You are viewing a plain text version of this content. The canonical link for it is here.

Posted to hdfs-dev@hadoop.apache.org by "Tsz Wo (Nicholas), SZE (JIRA)" <ji...@apache.org> on 2013/07/10 23:23:49 UTC

[jira] [Resolved] (HDFS-4645) Move from randomly generated block ID to sequentially generated block ID

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

Tsz Wo (Nicholas), SZE resolved HDFS-4645.
------------------------------------------

       Resolution: Fixed
    Fix Version/s:     (was: 3.0.0)
                   2.1.0-beta

+1 the branch-2 patch looks good.

Merged this to 2.1.0-beta.
                
> Move from randomly generated block ID to sequentially generated block ID
> ------------------------------------------------------------------------
>
>                 Key: HDFS-4645
>                 URL: https://issues.apache.org/jira/browse/HDFS-4645
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: namenode
>    Affects Versions: 3.0.0
>            Reporter: Suresh Srinivas
>            Assignee: Arpit Agarwal
>             Fix For: 2.1.0-beta
>
>         Attachments: editsStored, HDFS-4645.001.patch, HDFS-4645.002.patch, HDFS-4645.003.patch, HDFS-4645.004.patch, HDFS-4645.005.patch, HDFS-4645.006.patch, HDFS-4645.branch-2.patch, SequentialblockIDallocation.pdf
>
>
> Currently block IDs are randomly generated. This means there is no pattern to block ID generation and no guarantees such as uniqueness of block ID for the life time of the system can be made. I propose using SequentialNumber for block ID generation.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira