[ https://issues.apache.org/jira/browse/HDFS-4645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13696037#comment-13696037 ]
Hadoop QA commented on HDFS-4645: --------------------------------- {color:red}-1 overall{color}. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12590142/HDFS-4645.005.patch against trunk revision . {color:green}+1 @author{color}. The patch does not contain any @author tags. {color:green}+1 tests included{color}. The patch appears to include 11 new or modified test files. {color:green}+1 javac{color}. The applied patch does not increase the total number of javac compiler warnings. {color:green}+1 javadoc{color}. The javadoc tool did not generate any warning messages. {color:green}+1 eclipse:eclipse{color}. The patch built with eclipse:eclipse. {color:green}+1 findbugs{color}. The patch does not introduce any new Findbugs (version 1.3.9) warnings. {color:green}+1 release audit{color}. The applied patch does not increase the total number of release audit warnings. {color:red}-1 core tests{color}. The patch failed these unit tests in hadoop-hdfs-project/hadoop-hdfs: org.apache.hadoop.hdfs.tools.offlineEditsViewer.TestOfflineEditsViewer {color:green}+1 contrib tests{color}. The patch passed contrib unit tests. Test results: https://builds.apache.org/job/PreCommit-HDFS-Build/4578//testReport/ Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/4578//console This message is automatically generated. > 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, > 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