[ https://issues.apache.org/jira/browse/HDFS-1822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13019546#comment-13019546 ]
Tsz Wo (Nicholas), SZE commented on HDFS-1822: ---------------------------------------------- > ... In fact, these opcodes were released in 0.21. ... I forgot to say that opcodes can be changed in anytime as long as it is backward compatible, i.e. the new software can handle the old edit logs since opcodes are *private unstable* APIs; please see [{{FSEditLogOpCodes}}|http://svn.apache.org/viewvc/hadoop/hdfs/trunk/src/java/org/apache/hadoop/hdfs/server/namenode/FSEditLogOpCodes.java?view=annotate]. > Editlog opcodes overlap between 20 security and later releases > -------------------------------------------------------------- > > Key: HDFS-1822 > URL: https://issues.apache.org/jira/browse/HDFS-1822 > Project: Hadoop HDFS > Issue Type: Bug > Components: name-node > Affects Versions: 0.21.0, 0.22.0, 0.23.0 > Reporter: Suresh Srinivas > Assignee: Suresh Srinivas > Priority: Blocker > Fix For: 0.22.0, 0.23.0 > > Attachments: HDFS-1822.patch > > > Same opcode are used for different operations between 0.20.security, 0.22 and > 0.23. This results in failure to load editlogs on later release, especially > during upgrades. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira