[ https://issues.apache.org/jira/browse/HDFS-4645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13705101#comment-13705101 ]
Hudson commented on HDFS-4645: ------------------------------ Integrated in Hadoop-trunk-Commit #4062 (See [https://builds.apache.org/job/Hadoop-trunk-Commit/4062/]) In CHANGES.txt, move HDFS-4908 and HDFS-4645 to 2.1.0-beta. (Revision 1502009) Result = SUCCESS szetszwo : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1502009 Files : * /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt > 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