[ https://issues.apache.org/jira/browse/HDFS-2718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13196234#comment-13196234 ]
Aaron T. Myers commented on HDFS-2718: -------------------------------------- Hey Kosnt, given that this change is being done as a performance optimization, do you have any numbers on the performance gain of edits loading attained from this change? It seems like it should speed things up, and it's at least a good refactor that should make the code less obtuse, but I'd still like to make sure edits loading actually is faster after this change. > Optimize OP_ADD in edits loading > -------------------------------- > > Key: HDFS-2718 > URL: https://issues.apache.org/jira/browse/HDFS-2718 > Project: Hadoop HDFS > Issue Type: Bug > Components: name-node > Affects Versions: 0.22.0, 0.24.0, 1.0.0 > Reporter: Konstantin Shvachko > Assignee: Konstantin Shvachko > Attachments: editsLoader-0.22.patch, editsLoader-trunk.patch, > editsLoader-trunk.patch > > > During loading the edits journal FSEditLog.loadEditRecords() processes OP_ADD > inefficiently. It first removes the existing INodeFile from the directory > tree, then adds it back as a regular INodeFile, and then replaces it with > INodeFileUnderConstruction if files is not closed. This slows down edits > loading. OP_ADD should be done in one shot and retain previously existing > data. -- 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