[
https://issues.apache.org/jira/browse/HDFS-11096?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15707537#comment-15707537
]
Ming Ma commented on HDFS-11096:
--------------------------------
Thanks [~andrew.wang] [[email protected]] for bringing up this important
topic.
bq. this means we can't remove in 3.0 unless it was deprecated in 2.2.
To have comprehensive coverage, can we use static analysis tool to do cross
reference between branch 2 to trunk's source code, or JACC can handle that?
bq. This has been a problem even within just the 2.x line, so there's a real
need for better cross-version integration testing
Indeed. Such Investment will pay off in the long term, e.g. whatever
cross-version integration test system we come up can be used not only for 2.x
-> 3.x, but 2.x -> 2.y as well.
* Regarding how to automate binary and wired compatibility verification, we can
do something within the hadoop project first without integration with upper
layers. In addition, maybe there is a way to test it on a dev machine, for
example package 2.x jars into a container to run client or datanode, then test
it with 3.x containers. Or maybe some sort of setup using Jenkins + Docker
containers. This could have caught some of 2.x incompatibility issues.
* For prioritization, we can also evaluate the impact or there is any work
around. For example, we don't have to verify 2.7 -> 3.0 if we know 2.7 -> 2.8
and 2.8 -> 3.0 work.
* Rolling upgrade is important for high SLA data ingestion or maybe hbase
scenario. Without that, we have to fail over the entire cluster during upgrade.
> Support rolling upgrade between 2.x and 3.x
> -------------------------------------------
>
> Key: HDFS-11096
> URL: https://issues.apache.org/jira/browse/HDFS-11096
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: rolling upgrades
> Affects Versions: 3.0.0-alpha1
> Reporter: Andrew Wang
> Priority: Blocker
>
> trunk has a minimum software version of 3.0.0-alpha1. This means we can't
> rolling upgrade between branch-2 and trunk.
> This is a showstopper for large deployments. Unless there are very compelling
> reasons to break compatibility, let's restore the ability to rolling upgrade
> to 3.x releases.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
