[
https://issues.apache.org/jira/browse/HDFS-11096?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15710408#comment-15710408
]
Andrew Wang commented on HDFS-11096:
------------------------------------
Thanks for the comment Ming, inline:
bq. 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?
I think this is indeed handled by JACC. If you want to look at a sample report,
I set up a nightly job that runs JACC, e.g.
https://builds.apache.org/view/H-L/view/Hadoop/job/Hadoop-trunk-JACC/19/artifact/target/compat-check/report.html
We could really use some way of whitelisting issues, but I haven't figured that
out yet.
bq. maybe there is a way to test it on a dev machine,
Yea, the difficulty is building and maintaining this test framework. Perhaps
Bigtop can help? I think HBase has some integration tests using Docker also.
bq. 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.
Another idea to limit scope is to require a minimum 2.x version for 2.x-3.x
upgrades. HDFS-11096 proposes a min version of 2.1.0-beta, but we could
increase this to 2.7.1 or something instead.
bq. 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.
Got it. In terms of priority I think this still ranks below API, ABI, and
client/server wire compatibility, but it sounds like we still need it for
beta/GA.
> 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]
