hadoop-hdfs-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Todd Lipcon (JIRA)" <j...@apache.org>
Subject [jira] [Reopened] (HDFS-3644) OEV should recognize and deal with 0.20.20x opcode versions
Date Thu, 12 Jul 2012 18:05:35 GMT

     [ https://issues.apache.org/jira/browse/HDFS-3644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Todd Lipcon reopened HDFS-3644:

I disagree. There are people running systems with LV -19 which has the conflicted opcodes.
Currently if you run OEV on these logs, you end up getting errors because it reads delegation
token ops as eg symlink ops. If we don't support OEVing a given LV, we should raise an error.
> OEV should recognize and deal with 0.20.20x opcode versions
> -----------------------------------------------------------
>                 Key: HDFS-3644
>                 URL: https://issues.apache.org/jira/browse/HDFS-3644
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: tools
>    Affects Versions: 2.0.0-alpha, 3.0.0
>            Reporter: Todd Lipcon
>            Priority: Minor
> We have some opcode conflicts for edit logs between 0.20.20x (LV -19, -31) vs newer versions.
For edit log loading, we dealt with this by forcing users to save namespace on an earlier
version before upgrading. But, using a trunk OEV on an older version is useful since the OEV
has had so many improvements. It would be nice to be able to specify a flag to the OEV to
be able to run on older edit logs.

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


View raw message