You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by Erik Krogen <ek...@linkedin.com> on 2019/08/08 17:29:32 UTC
Re: [DISCUSS] Release 3.0.4 or branch-3.0 EOL
I'd like to revive this discussion. Today I see committers variously skipping backports to branch-3.0 and/or branch-3.1 (when backporting to branch-2, for example) and I'm concerned that we will have divergence between what commits are present in which branches.
Wei-Chiu, is Cloudera still rebasing on top of branch-3.1? If so then it seems we should be continuing to actively maintain it and not skipping any backports here.
If HDFS-13596 is fixed in branch-3.1/3.2, will it be possible to
rolling upgrade from Hadoop 2 to Hadoop 3.1/3.2? If the answer is yes,
I'm thinking we can drop 3.0 and consider 3.1+ only.
I agree on this front. I don't see any reason that we can't encourage upgrades from 2.x to 3.1+.
Should we initiate a vote to officially EOL the 3.0 line?
Thanks
Erik
________________________________
From: Akira Ajisaka <aa...@apache.org>
Sent: Sunday, May 26, 2019 11:55 PM
To: Hadoop Common <co...@hadoop.apache.org>
Subject: Re: [DISCUSS] Release 3.0.4 or branch-3.0 EOL
Thank you for your feedback,
> IMHO, I'd love to see HDFS-13596 <https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fissues.apache.org%2Fjira%2Fbrowse%2FHDFS-13596&data=02%7C01%7Cekrogen%40linkedin.com%7Ced0598246fcd4632c04908d6e2706c1c%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636945369809775515&sdata=I16mNOAXmsNUWEZ%2BBtjIR29NtknVc5bF5X2eZuh%2BvUY%3D&reserved=0> fixed to make it possible to rolling upgrade from Hadoop 2 to Hadoop 3.0
If HDFS-13596 is fixed in branch-3.1/3.2, will it be possible to
rolling upgrade from Hadoop 2 to Hadoop 3.1/3.2? If the answer is yes,
I'm thinking we can drop 3.0 and consider 3.1+ only.
Thanks,
Akira
On Wed, May 22, 2019 at 4:39 AM Ajay Kumar <aj...@cloudera.com> wrote:
>
> +1 for keeping no of active branches low, specially when it is not used actively.
>
> On Mon, May 20, 2019 at 3:33 AM Steve Loughran <st...@cloudera.com.invalid> wrote:
>>
>> I've been intermittently backporting things to it, but like you say: not
>> getting much active use.
>>
>>
>> 1. I'd like to view the 3.1 branch as the main "ready to play with"
>> Hadoop 3.x release, with 3.2 some new features.
>> 2. I'm planning on backporting some of the hadoop 3.x ABFS and S3A work
>> to that 3.x release, and for S3A, some to 3.1.x (and indeed, maybe we
>> should do the abfs connector, After all: it's not going to cause any
>> regressions).
>> 3. The hadoop-aws changes will include HADOOP-16117, AWS SDK update -
>> Sean Mackrory has been advocating "keep all active branches current with
>> the AWS SDKs", and I've come to agree. The testing there didn't find any
>> regressions, which was a pleasant surprise.
>> 4. For S3A, a big patch has just gone in, HADOOP-16085, which adds etag
>> and version columns to the S3Guard DDB tables, and uses these at load time.
>> Even if we don't backport that patch to the 3.1 line, it makes sense for
>> all 3.1.x clients to be updating the DB with the relevant columns as they
>> write it, so that on a mixed-client deployment, everyone keeps the table up
>> to date
>>
>>
>> As usual, help welcome, especially with testing
>>
>> -steve
>>
>> On Fri, May 17, 2019 at 12:15 PM Wei-Chiu Chuang <we...@apache.org> wrote:
>>
>> > Thanks for initiating the discussion, Akira.
>> >
>> > I've given similar thoughts on the possible EOL of Hadoop branch-3.0 line.
>> > IMHO, I'd love to see HDFS-13596
>> > <https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fissues.apache.org%2Fjira%2Fbrowse%2FHDFS-13596&data=02%7C01%7Cekrogen%40linkedin.com%7Ced0598246fcd4632c04908d6e2706c1c%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636945369809785518&sdata=Sx2X18h%2FXmuW%2BWTiWdlg3he4LYDNcoW0jY665GPgT3k%3D&reserved=0> fixed to make it
>> > possible to rolling upgrade from Hadoop 2 to Hadoop 3.0, and then roll
>> > another maint. release before we declare EOL.
>> >
>> > But in all seriousness, with my Cloudera hat on, CDH will soon rebase onto
>> > branch-3.1 so it's unlikely Cloudera can sponsor another 3.0 maint release.
>> > With my Apache hat on, Apache is an all-volunteer organization and we all
>> > act individually, but I am just being realistic that there would not be
>> > much motivation to roll another release in the future.
>> >
>> > Thoughts?
>> >
>> > On Fri, May 17, 2019 at 8:31 AM Akira Ajisaka <aa...@apache.org> wrote:
>> >
>> > > Hi folks,
>> > >
>> > > In branch-3.0, it is almost a year since 3.0.3 was released. Is there
>> > > any committer who wants to be a release manager of 3.0.4?
>> > >
>> > > If there are no users running Apache Hadoop 3.0.x in production, I'm
>> > > thinking we can stop maintaining branch-3.0. Please let me know there
>> > > are any users running Apache Hadoop 3.0.x.
>> > >
>> > > Any thoughts?
>> > >
>> > > -Akira
>> > >
>> > > ---------------------------------------------------------------------
>> > > To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
>> > > For additional commands, e-mail: common-dev-help@hadoop.apache.org
>> > >
>> > >
>> >
---------------------------------------------------------------------
To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-dev-help@hadoop.apache.org