[ https://issues.apache.org/jira/browse/HDFS-4645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Arpit Agarwal updated HDFS-4645: -------------------------------- Attachment: HDFS-4645.006.patch Thanks again Nicholas. I have addressed most of your feedback. I filed HDFS-4691 assigned to myself for this point since it might be a bit of refactoring of the existing code. {quote} The block id and generation stamp code actually should be moved to the blockmanagement package. See if you want to move the code here. Or we may do it later. {quote} > 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 > 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, 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