hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sanjay Radia (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-9517) Document Hadoop Compatibility
Date Thu, 30 May 2013 17:21:27 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-9517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13670509#comment-13670509
] 

Sanjay Radia commented on HADOOP-9517:
--------------------------------------

bq. wrt HDFS upgrade the current prose is not clear whether we permit HDFS metadata upgrades
w/in minor release or not.    ..... and explicitly say that metadata upgrades may only be
required for major version upgrades?
Agreed that it is not clear. Given that the conversion is automatic, do we want to allow metadata
*AND data* changes in minor releases ?  Or are we trying to say that rolling upgrades are
always possible in minor releases and hence we don't want to allow metadata and data changes?
Note although we have not figured out how to do rolling upgrades when there are metadata changes,
it may be possible to do so. BTW -upgrade is often used even when there are no metadata or
data changes as a safety measure.

bq. Let's clearly distinguish between HDFS upgrades (ie just upgrading the HDFS bits) from
an HDFS metadata upgrade, 
Given that this is in the data section I thought it was obvious. Lets modify the "Data" Section
to  start by saying that we are not talking about the executable bits.

bq. Also, what does "automatic conversion" mean, that the HDFS metadata upgrade process can
automatically convert the old version to the new? As opposed to requiring a user manually
perform multiple such upgrades?
Doesn't the word "automatic" clarify this? Again suggest some text improvements and we can
put it in.
                
> Document Hadoop Compatibility
> -----------------------------
>
>                 Key: HADOOP-9517
>                 URL: https://issues.apache.org/jira/browse/HADOOP-9517
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: documentation
>            Reporter: Arun C Murthy
>            Assignee: Karthik Kambatla
>         Attachments: hadoop-9517.patch, hadoop-9517.patch, hadoop-9517.patch, hadoop-9517.patch,
hadoop-9517-proposal-v1.patch, hadoop-9517-proposal-v1.patch
>
>
> As we get ready to call hadoop-2 stable we need to better define 'Hadoop Compatibility'.
> http://wiki.apache.org/hadoop/Compatibility is a start, let's document requirements clearly
and completely.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message