[ https://issues.apache.org/jira/browse/HDFS-362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Uma Maheswara Rao G updated HDFS-362: ------------------------------------- Status: Patch Available (was: Open) Hi Eli, I have updated the patch, can you please take a look. Also, i have changed the layoutversion to -39. With this change i have verified the following scenarios manually. *Scenario 1:* After the version change, verified the fsimgae loading. Successfully able to writing the fields and loading back. This i checked with eclipse debug points. *Scenario 2:* a)Created the namespace with -38 version with mutiple FS operations. b)Applied the patch which contains the version updation to -39. c)started the NN with upgrade option. Observation: Successfully able to load and start. And also finalized and rollbacked. Since old version of fsImage is required for upgrade verification, i have done the tests manually. And existing tests used for regression. --thanks > FSEditLog should not writes long and short as UTF8 and should not use > ArrayWritable for writing non-array items > --------------------------------------------------------------------------------------------------------------- > > Key: HDFS-362 > URL: https://issues.apache.org/jira/browse/HDFS-362 > Project: Hadoop HDFS > Issue Type: Improvement > Components: name-node > Reporter: Tsz Wo (Nicholas), SZE > Assignee: Uma Maheswara Rao G > Attachments: HDFS-362.1.patch, HDFS-362.2.patch, HDFS-362.patch > > > In FSEditLog, > - long and short are first converted to String and are further converted to > UTF8 > - For some non-array items, it first create an ArrayWritable object to hold > all the items and then writes the ArrayWritable object. > These result creating many intermediate objects which affects Namenode CPU > performance and Namenode restart. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira