[
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
I have taken care of other comments.
bq. How about removing dfsadmin command since a 2.x dfsadmin command won't run
against a build where distributed upgrade was supported
You mean remove dfsadmin -upgradeProgress command? Done.
I want do the following cleanup in another jira. These are non-compatible
changes. It should be okay to delete them, because this functionality has not
been used for a long time(last used in 0.14)
# Remove ClientProtocol#distributedUpgradeProgress(),
ClientProtocol#processUpgradeCommand
#* related protobuf methods, requests and responses
#* related java methods, request and responses
> 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
> Attachments: HDFS-2686.patch, HDFS-2686.patch, 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
