hadoop-hdfs-issues mailing list archives

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

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

Suresh Srinivas resolved HDFS-3644.
-----------------------------------

    Resolution: Won't Fix

This jira is not necessary. The conflict code was only in 0.20.203. Post upgrade to later
releases the conflicting opcode is not used. I am closing than as Won't Fix. Reopen if you
disagree.
                
> 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

        

Mime
View raw message