[
https://issues.apache.org/jira/browse/HDFS-2686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Suresh Srinivas updated HDFS-2686:
----------------------------------
Attachment: HDFS-2686.patch
Attached patch with all but the following comment addressed.
bq. Are you sure that renaming "distUpgradeVersion" to "unused" in hdfs.proto
is okay for backward comptibility?
Yes.
distUpgradeVersion is a required field. For compatibility:
# Old client that includes the removed field in protobuf message talks to a new
server. This is compatible, since the new server ignores the field.
# New client with the removed field talks to the old server. This is not
compatible, since the new server expects the field. This is handled by
retaining the unused field. The field name in hdfs.proto does not matter, as
long as field tag (2) remains the same.
> Rip out DistributedUpgrade framework
> ------------------------------------
>
> Key: HDFS-2686
> URL: https://issues.apache.org/jira/browse/HDFS-2686
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: data-node, name-node
> Affects Versions: 1.0.0, 2.0.0-alpha
> Reporter: Todd Lipcon
> Assignee: Suresh Srinivas
> Fix For: 3.0.0
>
> Attachments: HDFS-2686.patch, HDFS-2686.patch, HDFS-2686.patch
>
>
> A distributed upgrade framework was introduced long ago in HADOOP-1286 but
> was only used twice throughout history, and not since 0.17, where it was
> considered buggy (see HADOOP-3677). This is a lot of clutter in our codebase
> - let's consider removing it?
--
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
