hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Junping Du <...@hortonworks.com>
Subject Re: 2.7.3 release plan
Date Thu, 31 Mar 2016 15:10:45 GMT
Thanks for bringing up this topic, Sean. 
When I released our latest Hadoop release 2.6.4, the patch of HDFS-8791 haven't been committed
in so that's why we didn't discuss this earlier.
I remember in JIRA discussion, we treated this layout change as a Blocker bug that fixing
a significant performance regression before but not a normal performance improvement. And
I believe HDFS community already did their best with careful and patient to deliver the fix
and other related patches (like upgrade fix in HDFS-8578). Take an example of HDFS-8578, you
can see 30+ rounds patch review back and forth by senior committers, not to mention the outstanding
performance test data in HDFS-8791.
I would trust our HDFS committers' judgement to land HDFS-8791 on 2.7.3. However, that needs
Vinod's final confirmation who serves as RM for branch-2.7. In addition, I didn't see any
blocker issue to bring it into 2.6.5 now.
Just my 2 cents.

Thanks,

Junping

________________________________________
From: Sean Busbey <busbey@cloudera.com>
Sent: Thursday, March 31, 2016 2:57 PM
To: hdfs-dev@hadoop.apache.org
Cc: Hadoop Common; yarn-dev@hadoop.apache.org; mapreduce-dev@hadoop.apache.org
Subject: Re: 2.7.3 release plan

A layout change in a maintenance release sounds very risky. I saw some
discussion on the JIRA about those risks, but the consensus seemed to
be "we'll leave it up to the 2.6 and 2.7 release managers." I thought
we did RMs per release rather than per branch? No one claiming to be a
release manager ever spoke up AFAICT.

Should this change be included? Should it go into a special 2.8
release as mentioned in the ticket?

On Thu, Mar 31, 2016 at 1:45 AM, Akira AJISAKA
<ajisakaa@oss.nttdata.co.jp> wrote:
> Thank you Vinod!
>
> FYI: 2.7.3 will be a bit special release.
>
> HDFS-8791 bumped up the datanode layout version,
> so rolling downgrade from 2.7.3 to 2.7.[0-2]
> is impossible. We can rollback instead.
>
> https://issues.apache.org/jira/browse/HDFS-8791
> https://hadoop.apache.org/docs/stable/hadoop-project-dist/hadoop-hdfs/HdfsRollingUpgrade.html
>
> Regards,
> Akira
>
>
> On 3/31/16 08:18, Vinod Kumar Vavilapalli wrote:
>>
>> Hi all,
>>
>> Got nudged about 2.7.3. Was previously waiting for 2.6.4 to go out (which
>> did go out mid February). Got a little busy since.
>>
>> Following up the 2.7.2 maintenance release, we should work towards a
>> 2.7.3. The focus obviously is to have blocker issues [1], bug-fixes and *no*
>> features / improvements.
>>
>> I hope to cut an RC in a week - giving enough time for outstanding blocker
>> / critical issues. Will start moving out any tickets that are not blockers
>> and/or won’t fit the timeline - there are 3 blockers and 15 critical tickets
>> outstanding as of now.
>>
>> Thanks,
>> +Vinod
>>
>> [1] 2.7.3 release blockers:
>> https://issues.apache.org/jira/issues/?filter=12335343
>>
>



--
busbey

Mime
View raw message