• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
Yahoo! Hadoop User Group - May 2010 Meetup - Apache Hadoop Release Plans for 0.21.0, Tom White, Cloudera
 

Yahoo! Hadoop User Group - May 2010 Meetup - Apache Hadoop Release Plans for 0.21.0, Tom White, Cloudera

on

  • 2,577 views

 

Statistics

Views

Total Views
2,577
Views on SlideShare
2,065
Embed Views
512

Actions

Likes
0
Downloads
0
Comments
0

6 Embeds 512

http://developer.yahoo.com 265
http://developer.yahoo.net 187
http://www.slideshare.net 43
https://developer.yahoo.com 10
http://static.slidesharecdn.com 6
http://feeds.developer.yahoo.net 1

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    Yahoo! Hadoop User Group - May 2010 Meetup - Apache Hadoop Release Plans for 0.21.0, Tom White, Cloudera Yahoo! Hadoop User Group - May 2010 Meetup - Apache Hadoop Release Plans for 0.21.0, Tom White, Cloudera Presentation Transcript

    • Apache Hadoop 0.21 Release Plans Tom White tomwhite@apache.org 19 May 2010
    • Avoiding the quality death spiral Solaris went through a very interesting transition. Prior to Solaris 2.5, there was much more of a, for lack of a better word, waterfall model in terms of the way new releases were dispersed to people. As a result, people would not run the latest bits on their desktop or on the server; they would develop their own little bits and integrate them into a whole that they never saw. Solaris was in the quality death spiral because once people refused to use the latest stuf because it was known to be broken, then people used the latest stuf less and less and it got to be more and more broken. To break the quality death spiral, you’ve got to force people to use the latest stuf. I think it’s much more important when you’re in a distributed environment where you don’t necessarily have the kind of immediate peer pressure to do that. --Bryan Cantrill, http://queue.acm.org/detail.cfm?id=1413258
    • Release History
    • Source Compatibility
    • Process ▪ Fix blockers – http://bit.ly/common21blockers, hdfs21blockers, mapreduce21blockers ▪ Create build artifacts – First post split release ▪ Test – http://wiki.apache.org/hadoop/ReleaseTesting ▪ Vote and release ▪ Later 0.21.x bug fx releases for critical bugs or regressions
    • How to help out ▪ Fix blockers ▪ Try compiling your code against 0.21 ▪ Try out release candidates on your (test) cluster ▪ Try out releases on your (test) cluster ▪ Caveat emptor: 0.21.0 should not be used for production
    • What's in it? ▪ New, comprehensive MapReduce API ▪ Symlinks FileContext API (although not integrated with MapReduce) ▪ New shufe ▪ Hundreds of bug fxes and other improvements – https://svn.apache.org/repos/asf/hadoop/{common,hdfs,mapreduce}/branches/branch- 0.21/CHANGES.txt ▪ Not security (0.22 at end of year)
    • (c) 2008 Cloudera, Inc. or its licensors.  "Cloudera" is a registered trademark of Cloudera, Inc.. All rights reserved. 1.0