Re: June Hadoop Community Meetup

[Vinod Kumar Vavilapalli]

Plus general@ list.

Thanks
+Vinod

> On Jun 4, 2019, at 9:47 PM, Daniel Templeton  
> wrote:
> 
> The meetup page is now live:
> 
>https://www.meetup.com/Hadoop-Contributors/events/262055924
> 
> I'll fill in the agenda details after we get them nailed down.  The meetup 
> will be an all-day event on June 26th with lunch provided and a reception 
> after.  Let me know if there are any questions.
> 
> Hope to see you there!
> Daniel
> 
> On 5/23/19 10:57 AM, Daniel Templeton wrote:
>> Hi, all!  I want to let you know that Cloudera is planning to host a 
>> contributors meetup on June 26 at our Palo Alto headquarters. We're still 
>> working out the details, but we're hoping to follow the format that Oath and 
>> LinkedIn followed during the last two. Please feel free to reach out to me 
>> if you have a topic you'd like to propose for the meetup.  I will also be 
>> reaching out to key folks from the community to solicit ideas.  I will send 
>> out an update with more details when I have more to share.
>> 
>> Thanks!
>> Daniel
> 
> 
> -
> To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org
> For additional commands, e-mail: common-dev-h...@hadoop.apache.org
> 


-
To unsubscribe, e-mail: general-unsubscr...@hadoop.apache.org
For additional commands, e-mail: general-h...@hadoop.apache.org

Re: [ANNOUNCE] New Apache Hadoop committer: Jonathan Hung

[Vinod Kumar Vavilapalli]

Congratulations Jonathan, keep up the great work!

Thanks
+Vinod

> On May 18, 2018, at 2:56 PM, Konstantin Shvachko  wrote:
> 
> Hi all,
> 
> I am very glad to announce that Jonathan Hung was voted by the PMC as a
> Hadoop committer.
> Please join me to congratulate Jonathan with this well deserved status!
> 
> Thanks,
> --Konstantin


-
To unsubscribe, e-mail: general-unsubscr...@hadoop.apache.org
For additional commands, e-mail: general-h...@hadoop.apache.org

Re: [ANNOUNCE] New Apache Hadoop Committer: Shane Kumpf

[Vinod Kumar Vavilapalli]

Congratulations! Keep up the great work!

Thanks
+Vinod

> On May 15, 2018, at 4:59 AM, Shane Kumpf  wrote:
> 
> Thank you for all for the congratulations and recognition. I look forward
> to continuing to collaboration with this great community.
> 
> -Shane
> 
> On Mon, May 14, 2018 at 10:04 AM, Suma Shivaprasad <
> sumasai.shivapra...@gmail.com> wrote:
> 
>> Congrats Shane !
>> 
>> On Mon, May 14, 2018 at 8:07 AM, Eric Badger 
>> wrote:
>> 
>>> Always a pleasure to work with Shane and happy that he's getting the
>>> recognition he deserves! Congratulations, Shane!
>>> 
>>> Eric
>>> 
>>> On Mon, May 14, 2018 at 9:35 AM, Zian Chen 
>> wrote:
>>> 
 Congrats Shane!
> On May 13, 2018, at 10:01 PM, Rohith Sharma K S <
 rohithsharm...@apache.org> wrote:
> 
> Congratulations Shane!
> 
> -Rohith Sharma K S
> 
> On 13 May 2018 at 02:59, jhe  wrote:
> 
>> Hi All
>> 
>> It is my pleasure to announce that Shane Kumpf becomes a Hadoop
 Committer.
>> Please join me in congratulating Shane !
>> 
>> Jian
>> 
 
 
 -
 To unsubscribe, e-mail: general-unsubscr...@hadoop.apache.org
 For additional commands, e-mail: general-h...@hadoop.apache.org
 
 
>>> 
>> 


-
To unsubscribe, e-mail: general-unsubscr...@hadoop.apache.org
For additional commands, e-mail: general-h...@hadoop.apache.org

Re: [ANNOUNCE] New Hadoop Committer: Billie Rinaldi

[Vinod Kumar Vavilapalli]

Congratulations Billie, and keep up the great work!

Thanks
+Vinod

> On Nov 2, 2017, at 9:49 AM, Billie Rinaldi  wrote:
> 
> Thanks, everyone! Looking forward to working with the team in this new role.
> 
> Billie
> 
> On Fri, Oct 27, 2017 at 11:55 AM, Jian He  wrote:
> 
>> Hi All,
>> 
>> It is my pleasure to announce that the Apache Hadoop PMC voted to add
>> Billie Rinaldi as a committer in recognition of her continued contributions
>> to the project.
>> Please join me in congratulating Billie Rinaldi !
>> 
>> Best regards,
>> Jian
>> (on behalf of the Apache Hadoop PMC)
>> 


-
To unsubscribe, e-mail: general-unsubscr...@hadoop.apache.org
For additional commands, e-mail: general-h...@hadoop.apache.org

Re: [ANNOUNCE] Eric Payne added to the Apache Hadoop PMC

[Vinod Kumar Vavilapalli]

Congratulation and welcome aboard, Eric! Keep up the great work!

Thanks
+Vinod

> On Jul 25, 2017, at 2:05 PM, Jason Lowe  wrote:
> 
> It is my pleasure to announce that the Apache Hadoop PMC voted to add Eric 
> Payne as a member in recognition of his contributions to Apache Hadoop.
> Congratulations, Eric!
> Jason


-
To unsubscribe, e-mail: general-unsubscr...@hadoop.apache.org
For additional commands, e-mail: general-h...@hadoop.apache.org

[ANNOUNCE] Apache Hadoop 2.8.1 is released

[Vinod Kumar Vavilapalli]

Hi all,

The Apache Hadoop PMC has released version 2.8.1. You can get it from this 
page: http://hadoop.apache.org/releases.html#Download
This is a security release in the 2.8.0 release line. It consists of 2.8.0 plus 
security fixes. Users on 2.8.0 are encouraged to upgrade to 2.8.1.

Please note that 2.8.x release line continues to be not yet ready for 
production use. Critical issues are being ironed out via testing and downstream 
adoption. Production users should wait for a subsequent release in the 2.8.x 
line.

Thanks
+Vinod

Re: [ANNOUNCE] New PMC member Li Lu

[Vinod Kumar Vavilapalli]

Congratulations and keep up the great work!

+Vinod

> On Jan 10, 2017, at 10:29 AM, Wangda Tan  wrote:
> 
> Hi everyone,
> 
> I'm very pleased to announce that the Apache Hadoop PMC has voted to add
> Li Lu as a PMC member. This is in recognition of Li's many contributions to
> the Hadoop community.
> 
> Congratulations Li! Great work!
> 
> Best,
> Wangda Tan


-
To unsubscribe, e-mail: general-unsubscr...@hadoop.apache.org
For additional commands, e-mail: general-h...@hadoop.apache.org

Re: [ANNOUNCE] Apache Hadoop 2.7.3 Release

[Vinod Kumar Vavilapalli]

It looks like few mirrors are lagging - I sent the note after I got success 
from a couple of mirrors.

Please try other mirrors if you run into issues with one of them - things 
should work everywhere in less than a day.

Thanks
+Vinod

> On Aug 25, 2016, at 4:27 PM, Vinod Kumar Vavilapalli <vino...@apache.org> 
> wrote:
> 
> Hi all,
> 
> It gives me great pleasure to announce that the Apache Hadoop community has 
> voted to release Apache Hadoop 2.7.3.
> 
> Apache Hadoop 2.7.3 is the third minor release in the Hadoop-2.7.x line.
> 
> The release has 221 resolved issues with the following breakdown
> 
>   • 57 in Hadoop Common
>   • 79 in HDFS
>   • 57 in YARN
>   • 28 in MapReduce
> 
> Please see the Hadoop 2.7.3 Release Notes for a detailed list of issues 
> resolved.
> 
> The release news is posted on the Hadoop website too 
> (http://hadoop.apache.org/docs/r2.7.3/hadoop-project-dist/hadoop-common/releasenotes.html),
>  you can go to the downloads section directly 
> (http://hadoop.apache.org/releases.html#Download). The release documentation 
> is up at http://hadoop.apache.org/docs/r2.7.3/.
> 
> Thanks to everyone who contributed to the release!
> 
> +Vinod


-
To unsubscribe, e-mail: general-unsubscr...@hadoop.apache.org
For additional commands, e-mail: general-h...@hadoop.apache.org

[ANNOUNCE] Apache Hadoop 2.7.3 Release

[Vinod Kumar Vavilapalli]

Hi all,

It gives me great pleasure to announce that the Apache Hadoop community has 
voted to release Apache Hadoop 2.7.3.

Apache Hadoop 2.7.3 is the third minor release in the Hadoop-2.7.x line.

The release has 221 resolved issues with the following breakdown

• 57 in Hadoop Common
• 79 in HDFS
• 57 in YARN
• 28 in MapReduce

Please see the Hadoop 2.7.3 Release Notes for a detailed list of issues 
resolved.

The release news is posted on the Hadoop website too 
(http://hadoop.apache.org/docs/r2.7.3/hadoop-project-dist/hadoop-common/releasenotes.html),
 you can go to the downloads section directly 
(http://hadoop.apache.org/releases.html#Download). The release documentation is 
up at http://hadoop.apache.org/docs/r2.7.3/.

Thanks to everyone who contributed to the release!

+Vinod
-
To unsubscribe, e-mail: general-unsubscr...@hadoop.apache.org
For additional commands, e-mail: general-h...@hadoop.apache.org

Re: [ANNOUNCE] New Hadoop PMC Member - Sangjin Lee

[Vinod Kumar Vavilapalli]

Congratulations Sangjin! Keep up the great work and welcome aboard!

+Vinod

> On Apr 12, 2016, at 11:03 PM, Chris Nauroth  wrote:
> 
> On behalf of the Apache Hadoop PMC, I am very pleased to announce that
> Sangjin Lee has been elected as a PMC Member on the Apache Hadoop project,
> recognizing his continued contributions to the project so far.
> 
> Please join me in congratulating Sangjin!
> 
> --Chris Nauroth
> 
> 

Re: [ANNOUNCE] New Hadoop Committer - Naganarasimha Garla

[Vinod Kumar Vavilapalli]

Congratulations and welcome aboard, Naga!

Keep up the great efforts!

+Vinod

> On Apr 7, 2016, at 10:59 AM, Wangda Tan  wrote:
> 
> On behalf of the Apache Hadoop PMC, I am pleased to announce
> that Naganarasimha Garla has been elected a committer on the Apache Hadoop
> project.  We appreciate all of Naga's hard work thus far, and we look
> forward to his continued contributions.
> 
> Welcome onboard and congratulations, Naga!
> 
> Thanks,
> Wangda Tan

Re: [ANNOUNCE] New Hadoop Committer - Eric Payne

[Vinod Kumar Vavilapalli]

Congratulations, welcome aboard, and keep up the great contributions, Eric!

+Vinod

> On Feb 12, 2016, at 8:36 AM, Eric Payne  
> wrote:
> 
> Thank you all for you kind wishes and welcomes. It is an honor to work with 
> the Apache community.-Eric
> 
>  From: Jason Lowe 
> To: General  
> Sent: Thursday, February 11, 2016 9:52 AM
> Subject: [ANNOUNCE] New Hadoop Committer - Eric Payne
> 
> On behalf of the Apache Hadoop PMC, I am pleased to announce that Eric Payne 
> has been elected a committer on the Apache Hadoop project.  We appreciate all 
> of Eric's hard work thus far, and we look forward to his continued 
> contributions.
> 
> Welcome and congratulations, Eric!
> 
> Jason
> 
> 

[ANNOUNCE] Apache Hadoop 2.7.2 Release

[Vinod Kumar Vavilapalli]

Hi all,



It gives me great pleasure to announce that the Apache Hadoop community has 
voted to release Apache Hadoop 2.7.2.



Apache Hadoop 2.7.2 is the second minor release in the Hadoop-2.7.x line.



The release has 155 resolved issues with the following breakdown



24 in Hadoop Common
47 in HDFS
63 in YARN
21 MapReduce


Please see the Hadoop 2.7.2 Release Notes 

 for a detailed list of issues resolved.  The release news is posted on the 
Hadoop website too, you can go to the downloads section directly 
(http://hadoop.apache.org/releases.html#Download 
). The release documentation 
is up at http://hadoop.apache.org/docs/r2.7.2/ 
.



Thanks to everyone who contributed to the release!

+Vinod

[ANNOUNCE] Apache Hadoop 2.6.1 Release

[Vinod Kumar Vavilapalli]

It gives me great pleasure to announce that the Apache Hadoop community has
voted to release Apache Hadoop 2.6.1.


Hadoop 2.6.1 is the first point release in the Hadoop-2.6.x line. It almost
entirely is comprised of critical bug fixes (and their dependent patches)
done by the community on and backported from the 2.7 and the in-progress
2.8 lines.


The release has 158 resolved issues with the following breakdown

   - 21 in Hadoop Common
   - 56 in HDFS
   - 71 in YARN
   - 10 MapReduce


Please see the Hadoop 2.6.1 Release Notes

for the list of 158 bug fixes since the previous release 2.6.0.


The release news is posted on the Hadoop website too, you can go to the
downloads section directly (http://hadoop.apache.org/releases.html#Download
). The release documentation is up at http://hadoop.apache.org/docs/r2.6.1/.


Thanks to everyone who contributed to the release!


Special shout-out to Sangjin Lee and Akira Ajisaka who helped me with this
particularly long release process comprising of numerous patch backports.


+Vinod

Re: [ANNOUNCE] New Hadoop committer - Zhihai Xu

[Vinod Kumar Vavilapalli]

Congrats Zhihai! Keep up the great work!

+Vinod

 On Jul 30, 2015, at 12:36 PM, Karthik Kambatla ka...@cloudera.com wrote:
 
 On behalf of the Apache Hadoop PMC, I am pleased to announce that Zhihai Xu
 has been elected a committer on the Apache Hadoop project recognizing his
 prolific work in the last year or so.
 
 We appreciate Zhihai's hardwork thus far, and look forward to his
 contributions.
 
 Welcome Zhihai!
 
 Cheers!
 Karthik

Re: [ANNOUNCE] Apache Hadoop 2.7.1 Release

[Vinod Kumar Vavilapalli]

I forgot to push the local tag before, pushed it earlier in the day - you 
should see it now.

Thanks
+Vinod


 On Jul 14, 2015, at 2:44 PM, Rajat Jain rajat...@gmail.com wrote:
 
 Hello,
 
 Is there a release tag 2.7.1 created for the release? I see that branch-2.7
 is being updated with commits, so don't want to use the branch for my
 testing.
 
 Thanks,
 Rajat
 
 On Thu, Jul 9, 2015 at 12:43 AM, Tsuyoshi Ozawa oz...@apache.org wrote:
 
 Thanks for the release!
 
 FYI: A user reported me that a link to the release note page from
 download page was broken. I fixed it and published the page. Please
 let me know there is a problem.
 
 - Tsuyoshi
 
 On Thu, Jul 9, 2015 at 7:52 AM, Vinod Kumar Vavilapalli
 vino...@apache.org wrote:
 Hi all,
 
 
 It gives me great pleasure to announce that the Apache Hadoop community
 has
 voted to release Apache Hadoop 2.7.1.
 
 
 Hadoop 2.7.1 is the first minor release in the Hadoop-2.7.x line.
 
 
 This release is now considered the first stable release in 2.7.x line.
 It brings
 in a number of enhancements since the last stable release of 2.6.0. For a
 list of enhancements since 2.6.0, please navigate to the release
 documentation page http://hadoop.apache.org/docs/r2.7.1/.
 
 
 The release has 131 resolved issues with the following breakdown
 
 
 
   - 15 in Hadoop Common
   - 50 in HDFS
   - 55 in YARN
   - 11 MapReduce
 
 
 Please see the Hadoop 2.7.1 Release Notes
 
 http://hadoop.apache.org/docs/r2.7.1/hadoop-project-dist/hadoop-common/releasenotes.html
 
 for a detailed list of issues resolved.  The release news is posted on
 the
 Hadoop website too, you can go to the downloads section directly (
 http://hadoop.apache.org/releases.html#Download). The release
 documentation
 is up at http://hadoop.apache.org/docs/r2.7.1/.
 
 
 Thanks to everyone who contributed to the release!
 
 +Vinod
 

[ANNOUNCE] Apache Hadoop 2.7.1 Release

[Vinod Kumar Vavilapalli]

Hi all,


It gives me great pleasure to announce that the Apache Hadoop community has
voted to release Apache Hadoop 2.7.1.


Hadoop 2.7.1 is the first minor release in the Hadoop-2.7.x line.


This release is now considered the first stable release in 2.7.x line.
It brings
in a number of enhancements since the last stable release of 2.6.0. For a
list of enhancements since 2.6.0, please navigate to the release
documentation page http://hadoop.apache.org/docs/r2.7.1/.


The release has 131 resolved issues with the following breakdown



   - 15 in Hadoop Common
   - 50 in HDFS
   - 55 in YARN
   - 11 MapReduce


Please see the Hadoop 2.7.1 Release Notes
http://hadoop.apache.org/docs/r2.7.1/hadoop-project-dist/hadoop-common/releasenotes.html
for a detailed list of issues resolved.  The release news is posted on the
Hadoop website too, you can go to the downloads section directly (
http://hadoop.apache.org/releases.html#Download). The release documentation
is up at http://hadoop.apache.org/docs/r2.7.1/.


Thanks to everyone who contributed to the release!

+Vinod

[ANNOUNCE] Welcoming Junping Du to Apache Hadoop PMC

[Vinod Kumar Vavilapalli]

Hi all,

It gives me great pleasure to announce that Junping Du is welcomed to join
as a member of Apache Hadoop PMC. Here's appreciating all his work so far
into the project and looking forward to greater achievements in the future!

Please join me in welcoming Junping to Hadoop PMC!

Congratulations Junping!

Thanks,
+Vinod
On behalf of the Apache Hadoop PMC

Re: [ANNOUNCE] New Hadoop Committer - Rohith Sharma K S

[Vinod Kumar Vavilapalli]

Congrats Rohith!

+Vinod


 On Jul 7, 2015, at 1:24 PM, Jian He j...@hortonworks.com wrote:
 
 On behalf of the Apache Hadoop PMC, I am pleased to announce that Rohith 
 Sharma K S
 has been elected as a committer on the Apache Hadoop project.  We
 appreciate all of Rohith’s hard work thus far, and we look forward to his
 continued contributions.
 
 Thanks,
 Jian He

[ANNOUNCE] New Hadoop committer - Varun Vasudev

[Vinod Kumar Vavilapalli]

Hi all,


It gives me great pleasure to announce that the Apache Hadoop PMC recently
invited Varun Vasudev to become a committer in the project, to which he
accepted.


We deeply appreciate his efforts in the project so far, specifically in the
areas of YARN and MapReduce. Here’s looking forward to his
continued contributions going into the future!


Welcome aboard and congratulations, Varun!


+Vinod

On behalf of the Apache Hadoop PMC

Re: [ANNOUNCE] Apache Hadoop 2.7.0 Release

[Vinod Kumar Vavilapalli]

Marco Zühlke pinged me offline informing me that I completely got my 
issue-count wrong.

Seems like I had a very bizarre filter, I missed closing some tickets too at 
release time.

IAC, the following is the right breakdown.

The release has 923 resolved issues with the following breakdown (JIRA Filter: 
project in (YARN, HDFS, HADOOP, MAPREDUCE) AND resolution = Fixed AND 
fixVersion = 2.7.0)

259 in Hadoop Common
350 in HDFS
253 in YARN
  61 in MapReduce

Thanks Marco! And apologies everyone for my slip up.

+Vinod

On Apr 22, 2015, at 4:50 PM, Vinod Kumar Vavilapalli 
vino...@apache.orgmailto:vino...@apache.org wrote:


The release has 535 resolved issues with the following breakdown


  *   160 in Hadoop Common
  *   192 in HDFS
  *   148 in YARN
  *   35 MapReduce

[ANNOUNCE] Apache Hadoop 2.7.0 Release

[Vinod Kumar Vavilapalli]

Hi all,


It gives me great pleasure to announce that the Apache Hadoop community has
voted to release Apache Hadoop 2.7.0.


Hadoop 2.7.0 is the first major release for the year 2015 in the Hadoop-2.x
line, and brings a number of enhancements.


IMPORTANT NOTES


   - This release *drops* support for JDK6 runtime and works with JDK 7+
   *only*.
   - This release is *not* yet ready for production use. Critical issues
   are being ironed out via testing and downstream adoption. Production users
   should wait for a 2.7.1/2.7.2 release.


The release has 535 resolved issues with the following breakdown


   - 160 in Hadoop Common
   - 192 in HDFS
   - 148 in YARN
   - 35 MapReduce


Apache Hadoop 2.7.0 contains a number of significant enhancements. A few of
them are noted below.


Hadoop Common


   - HADOOP-9629 - Support Windows Azure Storage - Blob as a file system in
   Hadoop.

Hadoop HDFS


   - HDFS-3107 - Support for file truncate
   - HDFS-7584 - Support for quotas per storage type
   - HDFS-3689 - Support for files with variable-length blocks

Hadoop YARN


   - YARN-3100 - Make YARN authorization pluggable
   - YARN-1492 - Automatic shared, global caching of YARN localized
   resources (beta)

Hadoop MapReduce


   - MAPREDUCE-5583 - Ability to limit running Map/Reduce tasks of a job
   - MAPREDUCE-4815 - Speed up FileOutputCommitter for very large jobs with
   many output files.


 Please see the Hadoop 2.7.0 Release Notes
http://hadoop.apache.org/docs/r2.7.0/hadoop-project-dist/hadoop-common/releasenotes.html
for detailed list of issues resolved.  The release news is posted on the
Hadoop website too, you can go to the downloads section directly (
http://hadoop.apache.org/releases.html#Download)


Thanks to all those who contributed to the release!

+Vinod

[ANNOUNCE] Welcoming Zhijie Shen to Apache Hadoop PMC

[Vinod Kumar Vavilapalli]

Hi all,

On behalf of the Apache Hadoop PMC, it gives me great pleasure to announce that 
Zhijie Shen is recently welcomed to join as a member of Apache Hadoop PMC. 
Here's appreciating all his work so far into the project and looking forward to 
greater achievements in the future!

Please join me in welcoming Zhijie to Hadoop PMC! Congratulations Zhijie!

Thanks,
+Vinod


signature.asc
Description: Message signed with OpenPGP using GPGMail

[ANNOUNCE] Welcoming Jian He to Apache Hadoop PMC

[Vinod Kumar Vavilapalli]

Hi all,

On behalf of the Apache Hadoop PMC, it gives me great pleasure to announce that 
Jian He is recently welcomed to join as a member of Apache Hadoop PMC. Here's 
appreciating all his work so far into the project and looking forward to 
greater achievements in the future!

Please join me in welcoming Jian to Hadoop PMC! Congratulations Jian!

Thanks,
+Vinod


signature.asc
Description: Message signed with OpenPGP using GPGMail

Re: [ANNOUNCE] New Hadoop Committers - Akira Ajisaka and Tsuyoshi Ozawa

[Vinod Kumar Vavilapalli]

Congratulations, Akira and Tsuyoshi! Keep up the great work!

+Vinod

On Dec 17, 2014, at 7:55 AM, Steve Loughran ste...@hortonworks.com wrote:

 On behalf of the Apache Hadoop PMC, I am pleased to announce that Akira
 Ajisaka
 and Tsuyoshi Ozawa have been elected as committers on the Apache
 Hadoop project. We appreciate all the work they have put into the project
 so far, and look forward to their future contributions.
 
 Welcome, Akira  and Tsuyoshi!
 
 -Steve
 
 -- 
 CONFIDENTIALITY NOTICE
 NOTICE: This message is intended for the use of the individual or entity to 
 which it is addressed and may contain information that is confidential, 
 privileged and exempt from disclosure under applicable law. If the reader 
 of this message is not the intended recipient, you are hereby notified that 
 any printing, copying, dissemination, distribution, disclosure or 
 forwarding of this communication is strictly prohibited. If you have 
 received this communication in error, please contact the sender immediately 
 and delete it from your system. Thank You.



signature.asc
Description: Message signed with OpenPGP using GPGMail

Re: [ANNOUNCE] New Hadoop Committer - Vinayakumar B

[Vinod Kumar Vavilapalli]

Congrats Vinay Kumar! Welcome aboard!

Thanks,
+Vinod


On Thu, Apr 10, 2014 at 12:18 PM, Uma gangumalla umamah...@apache.orgwrote:

 Hi All,

   On behalf of the Apache Hadoop PMC, I am pleased to announce that
 Vinayakumar B has been elected as a committer in the Apache Hadoop
 project. We appreciate all the work Vinay has put into the project so
 far, and look forward to his future contributions.

 Welcome aboard, Vinay


 Regards,

 Uma

 On behalf of the Apache Hadoop PMC


-- 
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to 
which it is addressed and may contain information that is confidential, 
privileged and exempt from disclosure under applicable law. If the reader 
of this message is not the intended recipient, you are hereby notified that 
any printing, copying, dissemination, distribution, disclosure or 
forwarding of this communication is strictly prohibited. If you have 
received this communication in error, please contact the sender immediately 
and delete it from your system. Thank You.

[ANNOUNCE] New Hadoop Committer - Xuan Gong

[Vinod Kumar Vavilapalli]

Hi all,

I am very pleased to announce that the Apache Hadoop PMC voted in Xuan Gong
as a committer in the Apache Hadoop project. His contributions to YARN and
MapReduce have been outstanding! We appreciate all the work Xuan has put
into the project so far, and are looking forward to his future
contributions.

Welcome aboard, Xuan!

Thanks,
+Vinod
On behalf of the Apache Hadoop PMC

-- 
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to 
which it is addressed and may contain information that is confidential, 
privileged and exempt from disclosure under applicable law. If the reader 
of this message is not the intended recipient, you are hereby notified that 
any printing, copying, dissemination, distribution, disclosure or 
forwarding of this communication is strictly prohibited. If you have 
received this communication in error, please contact the sender immediately 
and delete it from your system. Thank You.

[ANNOUNCE] New Hadoop Committer - Omkar Vinit Joshi

[Vinod Kumar Vavilapalli]

Hi all,

I am very pleased to announce that Omkar Vinit Joshi is voted in as a
committer to the Apache Hadoop project. His contributions to YARN have been
nothing short of outstanding! We appreciate all the work Omkar has put into
the project so far, and are looking forward to his future contributions.

Welcome aboard, Omkar!

Thanks,
+Vinod
On behalf of the Apache Hadoop PMC

-- 
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to 
which it is addressed and may contain information that is confidential, 
privileged and exempt from disclosure under applicable law. If the reader 
of this message is not the intended recipient, you are hereby notified that 
any printing, copying, dissemination, distribution, disclosure or 
forwarding of this communication is strictly prohibited. If you have 
received this communication in error, please contact the sender immediately 
and delete it from your system. Thank You.

[ANNOUNCE] New Hadoop Committer - Ravi Prakash

[Vinod Kumar Vavilapalli]

Hi all,

I am very pleased to announce that Ravi Prakash is voted in as a committer
in the Apache Hadoop project. His contributions to Hadoop have been
outstanding! We appreciate all the work Ravi has put into the project so
far, and are looking forward to his future contributions.

Welcome aboard, Ravi!

Thanks,
+Vinod
On behalf of the Apache Hadoop PMC

-- 
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to 
which it is addressed and may contain information that is confidential, 
privileged and exempt from disclosure under applicable law. If the reader 
of this message is not the intended recipient, you are hereby notified that 
any printing, copying, dissemination, distribution, disclosure or 
forwarding of this communication is strictly prohibited. If you have 
received this communication in error, please contact the sender immediately 
and delete it from your system. Thank You.

[ANNOUNCE] New Hadoop Committer - Zhijie Shen

[Vinod Kumar Vavilapalli]

Hi all,

I am very pleased to announce that Zhijie Shen is voted in as a committer
in the Apache Hadoop project. His contributions to YARN and MapReduce have
been outstanding! We appreciate all the work Zhijie has put into the
project so far, and are looking forward to his future contributions.

Welcome aboard, Zhijie!

Thanks,
+Vinod
On behalf of the Apache Hadoop PMC

-- 
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to 
which it is addressed and may contain information that is confidential, 
privileged and exempt from disclosure under applicable law. If the reader 
of this message is not the intended recipient, you are hereby notified that 
any printing, copying, dissemination, distribution, disclosure or 
forwarding of this communication is strictly prohibited. If you have 
received this communication in error, please contact the sender immediately 
and delete it from your system. Thank You.

[ANNOUNCE] New Hadoop Committer - Mayank Bansal

[Vinod Kumar Vavilapalli]

Hi all,

I am very pleased to announce that Mayank Bansal is voted in as a committer
in the Apache Hadoop project. A long term Hadoop contributor, his
contributions to YARN and MapReduce have been outstanding! We appreciate
all the work Mayank has put into the project so far, and are looking forward
to his future contributions.

Welcome aboard, Mayank!

Thanks,
+Vinod
On behalf of the Apache Hadoop PMC

-- 
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to 
which it is addressed and may contain information that is confidential, 
privileged and exempt from disclosure under applicable law. If the reader 
of this message is not the intended recipient, you are hereby notified that 
any printing, copying, dissemination, distribution, disclosure or 
forwarding of this communication is strictly prohibited. If you have 
received this communication in error, please contact the sender immediately 
and delete it from your system. Thank You.

Re: [VOTE] change bylaws to add branch committers

[Vinod Kumar Vavilapalli]

Missed the vote. +1 after the fact.

Thanks,
+Vinod

On Aug 1, 2013, at 2:15 PM, Chris Douglas wrote:

 With 20 +1 votes (11 binding) the vote passes.
 
 Thanks to everyone who voted. -C
 
 On Wed, Jul 31, 2013 at 12:20 PM, Uma Maheswara Rao G
 hadoop@gmail.com wrote:
 +1 (binding)
 
 
 Regards,
 Uma
 
 
 On Fri, Jul 26, 2013 at 12:08 AM, Chris Douglas cdoug...@apache.org wrote:
 
 Discussion thread: http://s.apache.org/WhL
 
 The vote will run for 7 days. -C
 
 Index: main/author/src/documentation/content/xdocs/bylaws.xml
 ===
 --- main/author/src/documentation/content/xdocs/bylaws.xml
 (revision 1505876)
 +++ main/author/src/documentation/content/xdocs/bylaws.xml  (working
 copy)
 @@ -76,6 +76,13 @@
 commit access from the PMC. Such reinstatement is subject to
 consensus approval of active PMC members./p
 
 +pSignificant, pervasive features are often developed in a
 speculative
 +branch of the repository. The PMC may grant commit rights on the
 +branch to its consistent contributors, while the initiative is
 active.
 +Branch committers are responsible for shepherding their feature
 into
 +an active release and do not cast binding votes or vetoes in the
 +project./p
 +
 pAll Apache committers are required to have a signed Contributor
 License Agreement (CLA) on file with the Apache Software
 Foundation. There is a a
 @@ -220,6 +227,9 @@
  Consensus approval requires 3 binding +1 votes
  and no binding vetoes./li
 
 +li strongLazy Consensus -/strong
 + Lazy consensus requires no -1 votes ('silence gives
 assent')./li
 +
 li strongLazy Majority - /strong
  A lazy majority vote requires 3 binding +1
  votes and more binding +1 votes than -1 votes./li
 @@ -279,6 +289,12 @@
 
 pLazy 2/3 majority of PMC members/p/li
 
 + li strongNew Branch Committer/strong
 +
 +pWhen a branch committer is proposed for the PMC/p
 +
 +pLazy consensus of active PMC members/p/li
 +
  li strongNew Committer/strong
 
 pWhen a new committer is proposed for the project/p
 @@ -291,6 +307,13 @@
 
 pConsensus approval of active PMC members/p/li
 
 + li strongBranch Committer Removal/strong
 +
 +pWhen removal of commit privileges is sought
 strongor/strong
 +   when the branch is merged to the mainline/p
 +
 +pLazy 2/3 majority of active PMC members/p/li
 +
  li strongCommitter Removal/strong
 
 pWhen removal of commit privileges is sought.  Note: Such
 



signature.asc
Description: Message signed with OpenPGP using GPGMail

[ANNOUNCEMENT] New Committers in Apache Hadoop

[Vinod Kumar Vavilapalli]

Hi all,

The Apache Hadoop PMC is pleased to announce new committers:
 - Devaraj K and Sandy Ryza for their YARN/MR contributions and
 - Andew Wang for HDFS

Thanking them for all their past efforts, we hope to see them continue to move 
Apache Hadoop forward.

Thanks,
+Vinod



signature.asc
Description: Message signed with OpenPGP using GPGMail

Re: [RESULT] Release plan for Hadoop 2.0.5

[Vinod Kumar Vavilapalli]

There is a different vote thread that is happening on dev lists which 
potentially overrides this vote. You may want to hold on till that vote 
concludes.

Thanks,
+Vinod

On May 16, 2013, at 6:23 PM, Konstantin Boudnik wrote:
 
 I can do RM'ing for this release. I would highly appreciate any help from
 anyone who's interested in the stabilization of 2.0.x line of Hadoop.
 
 Thanks,
  Cos

Fwd: [VOTE] - Release 2.0.5-beta

[Vinod Kumar Vavilapalli]

There is a thread going on with a more specific release plan for 2.0.5-beta at 
common-dev@.

Please vote there.

Unlike the last vote where apparently it wasn't clear to some of the 
committers, stating clearly: all committers and PMC have binding votes for 
release plans according to Hadoop bylaws.

Thanks,
+Vinod Kumar Vavilapalli

Begin forwarded message:

 From: Arun C Murthy a...@hortonworks.com
 Subject: [VOTE] - Release 2.0.5-beta
 Date: May 15, 2013 10:57:30 AM PDT
 To: common-...@hadoop.apache.org
 Reply-To: common-...@hadoop.apache.org
 
 Folks,
 
 A considerable number of people have expressed confusion regarding the recent 
 vote on 2.0.5, beta status etc. given lack of specifics, the voting itself 
 (validity of the vote itself, whose votes are binding) etc.
 
 IMHO technical arguments (incompatibility b/w 2.0  2.1, current stability of 
 3 features under debate etc.) have been lost in the discussion in favor of 
 non-technical (almost dramatic) nuances such as seizing the moment. There 
 is now dangerous talk of tolerating incompatibility b/w 2.0 and 2.1) - this 
 is a red flag for me; particularly when there are just 3 features being 
 debated and active committers and contributors are confident of and ready to 
 stand by their work. All patches, I believe, are ready to be merged in the 
 the next few days per discussions on jira. This will, clearly, not delay the 
 other API work which everyone agrees is crucial. As a result, I feel no 
 recourse but to restart a new vote - all attempts at calm, reasoned, civil 
 discussion based on technical arguments have come to naught - I apologize for 
 the thrash caused to everyone's attention.
 
 To get past all of this confusion, I'd like to present an alternate, specific 
 proposal for consideration.
 
 I propose we continue the original plan and make a 2.0.5-beta release by May 
 end with the following content:
 # HDFS-347
 # HDFS Snapshots
 # Windows support
 # Necessary  final API/protocol changes such as:
 * Final YARN API changes: YARN-386
 * MR Binary Compatibility: MAPREDUCE-5108
 * Final RPC cleanup: HADOOP-8990
 
 People working on the above features have all expressed considerable comfort 
 with them and are ready to stand-by to help expedite any necessary bug-fixes 
 etc. to get to stabilization quickly. I'm confident we can get this release 
 out by end of May. This sets stage for a hadoop-2.x GA release right after 
 with some more testing - this means I think I can quickly turn around and 
 make bug-fix releases as necessary right after 2.0.5-beta.
 
 I request that people consider helping out with this plan and sign up to help 
 push hadoop-2.x to stability as outlined above. I believe this will help 
 achieve our shared goals of quickly stabilizing hadoop-2 and help ensure we 
 can support it for forseeable future in a compatible manner for the benefit 
 of our users and downstream projects.
 
 Please vote, the vote will run the normal 7 days. Obviously, I'm +1.
 
 thanks,
 Arun
 
 PS: To keep this discussion grounded in technical details I've moved this to 
 dev@ (bcc general@).
 

Re: [RESULT] Release plan for Hadoop 2.0.5

[Vinod Kumar Vavilapalli]

The vote count is wrong:

6 binding +1s
5 binding -1s
4 non-binding +1s
2 non-binding -1s.

I think you mis-counted stevel, whose vote is binding.

On May 14, 2013, at 10:07 AM, Konstantin Shvachko wrote:

 This vote passes with
 6 binding +1s
 4 non-binding +1
 4 binding -1
 3 non-binding -1
 
 Thank you for voting,
 --Konstantin
 
 
 On Wed, May 1, 2013 at 12:53 PM, Konstantin Shvachko
 shv.had...@gmail.comwrote:
 
 Please vote on the following plan for Hadoop release 2.0.5
 - bug fixes encountered in current release 2.0.4-alpha
 - make all API changes to allow freezing them post 2.0.5
 - no new features
 
 As discussed on @dev thread
 http://s.apache.org/fs
 this will allow to stabilize 2.0 branch in a short and predictable period
 of time.
 This enables a powerful option to have the release tested at Yahoo scale.
 The plan is to follow up with 2.1.0 - the stable release.
 New features can and should be added on top of the stable release once it
 is out.
 
 Hadoop by-laws:
 http://hadoop.apache.org/bylaws.html
 
 Release Plan
 Defines the timetable and actions for a release. The plan also nominates a
 Release Manager.
 Lazy majority of active committers
 
 assume nomination of a Release Manager with the plan.
 It would be really good if Arun continues if this plan is adopted.
 We can return to the RM topic if not.
 
 The vote will run for 7 days until next Wed, May 8th.
 
 Thanks,
 --Konstantin
 

Re: [RESULT] Release plan for Hadoop 2.0.5

[Vinod Kumar Vavilapalli]

Have no idea what you meant there.

Even though several others noted that it isn't clear what is being voted on, 
trying to make sense out of it, it seems that
 - you don't want any new features at all in 2.0.5.
 - The originally planned 2.0.5 *has* already got new features which go against 
this vote result.

So I think, Arun proposed that we rename the originally planned 2.0.5 to 2.1 
and you said yes. Arun then he went ahead and copied 2.0.4-alpha to 2.0-alpha 
where it can be 'stabilized'.

And then this.

Please make it clear. Unfortunately there are those who have the onus of 
reviewing/committing some 'features' to branch-2. Please let us know what is 
okay.

Will start committing to branch-2 unless I hear otherwise.

The other concern is about merging patches into this 'stability-branch'. 
Clearly the vote doesn't tell who the RM is and it isn't clear who is doing it. 
Till that happens, I'll skip merging patches to branch-2.0-alpha branch - 
whether the patch is a feature or a bug needs to be negotiated with the RM 
*when in doubt*.

Thanks,
+Vinod

On May 14, 2013, at 11:52 AM, Konstantin Shvachko wrote:

 Sounds like you are having fun, Arun.
 2.0.5 is explicitly in the subject line for this vote.
 No worries I'll fix that.
 
 You should stop assuming - it's in nobody interests - and start reading.
 --Konst
 
 
 On Tue, May 14, 2013 at 11:10 AM, Arun C Murthy a...@hortonworks.com wrote:
 
 
 On May 14, 2013, at 11:04 AM, Konstantin Shvachko wrote:
 
 I can point you towards a set of fixes I think important for YARN
 (nodemanager, security etc.).
 
 That would be very much appreciated.
 
 I'll do the 2.1 series by renaming the planned 2.0.5 to 2.1.
 
 Thanks.
 
 
 Thanks. I've copied branch-2.0.4-alpha as a new branch-2.0-alpha branch.
 
 This way you can start with a clean slate. Good luck.
 
 As I noted before in the thread, the APIs in branch-2.0-alpha will remain
 incompatible with branch-2.
 
 thanks,
 Arun

Re: [VOTE] Release plan for Hadoop 2.0.5

[Vinod Kumar Vavilapalli]

That's a problem, if it isn't in the vote as to what feature in progress is 
being proposed to be included and what is excluded, how can we expect to vote?

Thanks,
+Vinod

On May 9, 2013, at 11:39 PM, Konstantin Shvachko wrote:

 Vinod,
 
 I did ask Arun for the set of features for the release, and did ask to put
 it on vote.
 It is deep in the discussion thread, but you can find it.
 
 Thank you for voting,
 --Konst
 
 
 On Thu, May 9, 2013 at 5:25 PM, Vinod Kumar Vavilapalli 
 vino...@hortonworks.com wrote:
 
 
 Confused and thought this was dead as the discussion was happening in
 parallel. I wish this vote was retracted while the discussion reaches some
 conclusion.
 
 My concerns:
 - As you noted in the by-laws, this plan should also nominate the RM. Or
 if Arun is doing this, he should accept this? And may be call the vote for
 release plan himself? The bylaws aren't clear about this, but that only
 seems natural - you manage a release and so you call for a vote on the
 plan, no?
 - It's not clear what happens of features that are half-way through. That
 needs to be spelled out.
 - Even otherwise, we can always add features without destabilizing the
 current release at all if we can switch the feature off with one flag.
 Arguable on a case-by-case basis but possible.
 - Also,  it isn't always clear what a feature is and what isn't. For e.g,
 the ResourceManager restart work in YARN can be called a feature or a bug
 depending on the context.
 
 In all the above cases, we should discuss on whether a feature can be
 merged in or not on a case-by-case basis instead of a blanket no.
 
 -1 (binding)
 
 Thanks,
 +Vinod
 Side note: The bylaws repeatedly talk of active committers and active
 PMC members, it makes sense, but we should clarify that.
 
 On May 1, 2013, at 12:53 PM, Konstantin Shvachko wrote:
 
 Please vote on the following plan for Hadoop release 2.0.5
 - bug fixes encountered in current release 2.0.4-alpha
 - make all API changes to allow freezing them post 2.0.5
 - no new features
 
 As discussed on @dev thread
 http://s.apache.org/fs
 this will allow to stabilize 2.0 branch in a short and predictable period
 of time.
 This enables a powerful option to have the release tested at Yahoo scale.
 The plan is to follow up with 2.1.0 - the stable release.
 New features can and should be added on top of the stable release once it
 is out.
 
 Hadoop by-laws:
 http://hadoop.apache.org/bylaws.html
 
 Release Plan
 Defines the timetable and actions for a release. The plan also nominates
 a
 Release Manager.
 Lazy majority of active committers
 
 assume nomination of a Release Manager with the plan.
 It would be really good if Arun continues if this plan is adopted.
 We can return to the RM topic if not.
 
 The vote will run for 7 days until next Wed, May 8th.
 
 Thanks,
 --Konstantin
 
 

Re: [VOTE] Release plan for Hadoop 2.0.5

[Vinod Kumar Vavilapalli]

Confused and thought this was dead as the discussion was happening in parallel. 
I wish this vote was retracted while the discussion reaches some conclusion.

My concerns:
- As you noted in the by-laws, this plan should also nominate the RM. Or if 
Arun is doing this, he should accept this? And may be call the vote for release 
plan himself? The bylaws aren't clear about this, but that only seems natural - 
you manage a release and so you call for a vote on the plan, no?
- It's not clear what happens of features that are half-way through. That needs 
to be spelled out.
- Even otherwise, we can always add features without destabilizing the current 
release at all if we can switch the feature off with one flag. Arguable on a 
case-by-case basis but possible. 
- Also,  it isn't always clear what a feature is and what isn't. For e.g, the 
ResourceManager restart work in YARN can be called a feature or a bug depending 
on the context.

In all the above cases, we should discuss on whether a feature can be merged in 
or not on a case-by-case basis instead of a blanket no.

-1 (binding)

Thanks,
+Vinod
Side note: The bylaws repeatedly talk of active committers and active PMC 
members, it makes sense, but we should clarify that.

On May 1, 2013, at 12:53 PM, Konstantin Shvachko wrote:

 Please vote on the following plan for Hadoop release 2.0.5
 - bug fixes encountered in current release 2.0.4-alpha
 - make all API changes to allow freezing them post 2.0.5
 - no new features
 
 As discussed on @dev thread
 http://s.apache.org/fs
 this will allow to stabilize 2.0 branch in a short and predictable period
 of time.
 This enables a powerful option to have the release tested at Yahoo scale.
 The plan is to follow up with 2.1.0 - the stable release.
 New features can and should be added on top of the stable release once it
 is out.
 
 Hadoop by-laws:
 http://hadoop.apache.org/bylaws.html
 
 Release Plan
 Defines the timetable and actions for a release. The plan also nominates a
 Release Manager.
 Lazy majority of active committers
 
 assume nomination of a Release Manager with the plan.
 It would be really good if Arun continues if this plan is adopted.
 We can return to the RM topic if not.
 
 The vote will run for 7 days until next Wed, May 8th.
 
 Thanks,
 --Konstantin

Re: Status of 2.0.4-alpha release

[Vinod Kumar Vavilapalli]

Great news! We can go forward with releasing 2.0.4-alpha now, thanks!

+Vinod Kumar Vavilapalli

On Apr 3, 2013, at 3:29 PM, Roman Shaposhnik wrote:

 Hi!
 
 Thanks to the tireless work of the Bigtop and Hadoop committers
 we've made quite a bit of progress on 2.0.4-alpha. The build
 pipeline that we've setup seems to be rather nice (and perhaps
 could be utilized for all future releases of Hadoop). The first
 stage of the pipeline is available here:
https://builds.apache.org/view/Hadoop/job/Hadoop-branch-2.0.4/
 and the second one over here:

 http://bigtop01.cloudera.org:8080/view/Bigtop-trunk/job/Bigtop-trunk-Hadoop/
 
 Anybody who's interested in helping with a release is more than
 welcome to get either tarballs or packages from these 2 jobs.
 
 As far as testing is concerned we're now completely unblocked
 for both unsecure and fully kerberized testing modes and Bigtop
 is proceeding with the rest of the testing process. We've got
 4 unit test failures left:

 https://builds.apache.org/view/Hadoop/job/Hadoop-branch-2.0.4/lastCompletedBuild/testReport/
 which I'm going to file JIRAs for.
 
 Given that I don't see any current showstoppers in ASF JIRA
 and hoping that the rest of Bigtop testing doesn't discover
 anything major do you guys think we can release sometime
 next week?
 
 Thanks,
 Roman.

Re: hadoop-2.0.4-alpha bug-fix release

[Vinod Kumar Vavilapalli]

I just checked in YARN-509/HADOOP-9444.

Thanks,
+Vinod Kumar Vavilapalli

On Mar 28, 2013, at 9:02 AM, Roman Shaposhnik wrote:

 Also, we are not out of the woods yet. The Hadoop build out of the
 2.0.4-alpha branch
 still seem to have issues with Kerberos deployments. Here's the first
 in a series
 of JIRAs:
 https://issues.apache.org/jira/browse/YARN-509

Re: [DISCUSS] stabilizing Hadoop releases wrt. downstream

[Vinod Kumar Vavilapalli]

Replies inline.


 for the past couple of releases of Hadoop 2.X code line the issue
 of integration between Hadoop and its downstream projects has
 become quite a thorny issue. The poster child here is Oozie, where
 every release of Hadoop 2.X seems to be breaking the compatibility
 in various unpredictable ways. At times other components (such
 as HBase for example) also seem to be affected.
 
 Now, to be extremely clear -- I'm NOT talking about the *latest* version
 of Oozie working with the *latest* version of Hadoop, instead
 my observations come from running previous *stable*  releases
 of Bigtop on top of Hadoop 2.X RCs.


As you yourself noted later, the pain is part of the 'alpha' status of the 
release. We are targeting one of the immediate future releases to be a beta and 
so these troubles are really only the short term.


 Do you guys think that the project have reached a point where integration
 and compatibility issues should be prioritized really high on the list
 of things that make or break each future release?


You should see the other discussion where we discussed about this very question 
of stability of our immediate future releases.


 The good news, is that Bigtop's charter is in big part *exactly* about
 providing you with this kind of feedback. We can easily tell you when
 Hadoop behavior, with regard to downstream components, changes
 between a previous stable release and the new RC (or even branch/trunk).
 What we can NOT do is submit patches for all the issues. We are simply
 too small a project and we need your help with that.


I think there is a fundamental problem with the interaction of Bigtop with the 
downstream projects, if nothing else, with Hadoop. We never formalized on the 
process, will BigTop step in after an RC is up for vote or before? As I see it, 
 it's happening after the vote is up, so no wonder we are in this state. Shall 
we have a pre-notice to Bigtop so that it can step in before?


 I would argue that moving forward this is a really unfortunate
 situation that may end up undermining the long term success
 of Hadoop 2.X if we don't start addressing the problem. Think
 about it -- 90% of unit tests that run downstream on Apache
 infrastructure are still exercising Hadoop 1.X underneath.
 In fact, if you were to forcefully make, lets say, HBase's
 unit tests run on top of Hadoop 2.X quite a few of them
 are going to fail. Hadoop community is, in effect, cutting
 itself off from the biggest source of feedback -- its downstream
 users. This in turn:
 
   * leaves Hadoop project in a perpetual state of broken
 windows syndrome.
 
   * leaves Apache Hadoop 2.X releases in a state considerably
 inferior to the releases *including* Apache Hadoop done by the
 vendors. The users have no choice but to alight themselves
 with vendor offerings if they wish to utilize latest Hadoop functionality.
 The artifact that is know as Apache Hadoop 2.X stopped being
 a viable choice thus fracturing the user community and reducing
 the benefits of a commonly deployed codebase.
 
* leaves downstream projects of Hadoop  in a jaded state where
  they legitimately get very discouraged and frustrated and eventually
  give up thinking that -- well, we work with one release of Hadoop
  (the stable one Hadoop 1.X) and we shall wait for the Hadoop
  community to get their act together.
 
 It is about time Hadoop 2.X community wins back all those end users
 and downstream projects that got left behind during the alpha
 stabilization phase.


This is overblown, we've been working with various downstream projects - Hbase, 
Hive, Pig, Oozie to help them transition them to 2.x and I believe we've made 
significant progress already.

Sure enough, there are continuing pains, but these are part of the alpha 
status. If we are really looking forward to a stable release which can support 
going forward, we need to live with and dive past these short term pains. I'd 
rather like us swim through these now instead of support broken APIs and 
features in our beta, having seen this very thing happen with 1.*.

Let's fix the way the release related communication is happening across our 
projects so that we can all work together and make 2.X a success.

Thanks,
+Vinod

Re: [DISCUSS] Clarify bylaws on PMC chair voting

[Vinod Kumar Vavilapalli]

+1 to Owen's suggestion.

Bobby, recall that PMC Chair is (just) a representative who communicates with 
the board on behalf of the PMC, and not any sort of leader (See 
http://www.apache.org/dev/pmc.html#chair); all the project decisions are driven 
by the PMC collectively. Given that,  one should not expect vetoes at all in 
this vote.

Thanks,
+Vinod

On Nov 13, 2012, at 7:25 AM, Robert Evans wrote:

 The current bylaws state that the PMC chair recommendation to the apache
 board should be based off of lazy consensus.  That means that any PMC
 member can -1(veto) a candidate so long as they give a valid reason with
 the veto. The validity of the reason for the veto if challenged can be
 confirmed by another PMC member.  I am fine with the proposal to use STV.
 However, I don't think in practice it really matters if we allow for
 vetoes or not.  If someone really feels strongly enough to veto a
 candidate, they would also feel strongly enough make their reason known
 during the voting and discussion on the candidate. If the reason is valid
 enough to withstand a challenge I would suspect it would also be valid
 enough to influence any voting process we set up.  I don't care what
 voting process we use, I just care that the bylaws are clarified to pick
 one that can handle one or more candidates.
 
 -- Bobby
 
 On 11/12/12 5:53 PM, Owen O'Malley omal...@apache.org wrote:
 
 Thanks, Nicholas.
 
 I think the vote for PMC chair should be a straight majority vote with STV
 used in the case of more than 2 choices. Using +1 and/or -1's when voting
 in a multiple choice seems confused and likely to cause more problems than
 it solves.
 
 -- Owen
 

Re: [VOTE] 0.23.4 release

[Vinod Kumar Vavilapalli]

Great news! Thanks for the update, Bobby!

Thanks,
+Vinod Kumar Vavilapalli
Hortonworks Inc.
http://hortonworks.com/

On Oct 15, 2012, at 12:55 PM, Robert Evans wrote:

 From my count we have 5 binding +1 votes and no -1s so it passes.  I will 
 upgrade nexus and move the tag to its final value.
 
 Thanks for the help from everyone.
 
 On a related note I am happy to say that 0.23.3 has moved to an even larger 
 grid at Yahoo!. Today we are now running 0.23.3 on a 3,600 node cluster, 
 still with no new issues beyond those we saw on the previous 2000 node 
 cluster.  There is still some polishing to do, but YARN is looking fairly 
 good so far.  Which is great because this cluster has a few production jobs 
 running on it :).
 
 --Bobby 
 
 -Original Message-
 From: Robert Evans [mailto:ev...@yahoo-inc.com] 
 Sent: Monday, October 08, 2012 12:12 PM
 To: general@hadoop.apache.org
 Subject: Re: [VOTE] 0.23.4 release
 
 Thanks for catching that.  There was a bug in my script that I used to
 build everything for the release.  It rebuilt the src tag ball after I had
 signed the original.  The contents are the same, but the date/time stamps
 were off.  I uploaded a new version of the offending tar.gz with the
 corresponding signature and mds files.
 
 Thanks again,
 
 Bobby
 
 On 10/8/12 1:51 PM, Siddharth Seth seth.siddha...@gmail.com wrote:
 
 Bobby, the checksums don't match for hadoop-0.23.4-src.tar.tar.gz.
 
 Thanks
 - Sid
 
 On Mon, Oct 8, 2012 at 8:06 AM, Robert Evans ev...@yahoo-inc.com wrote:
 
 Thanks for the help everyone on this.  I have re-spun the release.  You
 can get it at
 
 https://svn.apache.org/repos/asf/hadoop/common/tags/release-0.23.4-rc2
 http://people.apache.org/~bobby/hadoop-0.23.4-candidate-2/
 
 And through the apache maven staging repository.
 
 The only difference is some debugging code removed.  The vote now goes
 until Monday 15th. I am a +1 for the release.
 
 --Bobby Evans
 
 On 10/5/12 2:41 PM, Robert Evans ev...@yahoo-inc.com wrote:
 
 Arun, if you could re-spin it I would be happy to let you.  If not I
 can
 do it myself on Monday.  My box that is set up to do the builds is
 offline
 until Monday.  There are some workman fixing some things in my cube
 this
 weekend.
 
 Thanks for your help,
 
 Bobby
 
 On 10/5/12 1:46 PM, Arun Murthy a...@hortonworks.com wrote:
 
 I think Bobby is OOO, I can re-spin if Thomas can't step in.
 
 Arun
 
 Sent from my iPhone
 
 On Oct 5, 2012, at 11:44 AM, Owen O'Malley omal...@apache.org wrote:
 
 Bobby,
 It looks like some debugging code got committed and rolled into the
 release. I think we'll need to re-spin the rc after fixing it, so
 -1.
 
 Thanks,
  Owen
 
 
 
 



signature.asc
Description: Message signed with OpenPGP using GPGMail

Re: [VOTE] Release hadoop-2.0.2-alpha

[Vinod Kumar Vavilapalli]

I verified this RC, based on my usual check-list:

 - Signatures and message digests are good.
 - The top level full LICENSE, NOTICE and README for both the source and binary 
artifacts are good
 - CHANGES.txt for common, hdfs, mapred and YARN are correctly located.
 - Able to build the tar.gzs out of the expanded source tar ball.

Testing: All testing on single node, unsecured, default mode. Built from the 
sources (not from the convenience binary artifacts)
  - Separate installation homes for *all* the sub-projects
  - Started HDFS daemons successfully
  - Successfully started YARN daemons - ResourceManager and NodeManager
  - Successfully started mapreduce history server.
  - Ran the distributed shell and the pi mapreduce example successfully

+1 for the latest RC.

Thanks,
+Vinod Kumar Vavilapalli
Hortonworks Inc.
http://hortonworks.com/

On Oct 1, 2012, at 8:52 PM, Arun C Murthy wrote:

 Folks,
 
 I've created another release candidate (RC2) for hadoop-2.0.2-alpha that I 
 would like to release.  
 
 The highlights of the release are several bug-fixes and stabilization of 
 YARN/MapReduce; also includes significant enhancements to HDFS HA.
 
 The RC is available at: 
 http://people.apache.org/~acmurthy/hadoop-2.0.2-alpha-rc2/
 The RC tag in svn is here: 
 http://svn.apache.org/viewvc/hadoop/common/tags/release-2.0.2-alpha-rc2/
 The maven artifacts are available via repository.apache.org.
 
 Please try the release and vote; the vote will run for the usual 7 days.
 
 thanks,
 Arun
 
 --
 Arun C. Murthy
 Hortonworks Inc.
 http://hortonworks.com/
 
 



signature.asc
Description: Message signed with OpenPGP using GPGMail

Re: [VOTE] Release hadoop-2.0.2-alpha

[Vinod Kumar Vavilapalli]

Hey Arun, I'd like to get in YARN-9 + HADOOP-8794 and MAPREDUCE-4649 before we 
make another release. The less number of releases with the inconsistent env var 
names, the better. Shouldn't take more than a couple of days before these 
patches can get committed. What do you think?

Thanks,
+Vinod

On Sep 16, 2012, at 7:19 PM, Arun C Murthy wrote:

 Folks,
 
 I've created a release candidate (rc0) for hadoop-2.0.2-alpha that I would 
 like to release.  
 
 The highlights of the release are several bug-fixes and stabilization of 
 YARN/MapReduce.
 
 The RC is available at: 
 http://people.apache.org/~acmurthy/hadoop-2.0.2-alpha-rc0/
 The RC tag in svn is here: 
 http://svn.apache.org/viewvc/hadoop/common/tags/release-2.0.2-alpha-rc0/
 The maven artifacts are available via repository.apache.org.
 
 Please try the release and vote; the vote will run for the usual 7 days.
 
 thanks,
 Arun
 
 
 --
 Arun C. Murthy
 Hortonworks Inc.
 http://hortonworks.com/
 
 

Re: [VOTE] 0.23.3 release

[Vinod Kumar Vavilapalli]

Bobby, seems like you've already created the tag. Please also remove 
branches/branch-0.23.3 and tags/release-0.23.0-rc0.

You also need to update the site adding links to the new release, let me know 
if you need any help.

Thanks,
+Vinod

On Sep 14, 2012, at 2:56 PM, Robert Evans wrote:

 With 5 binding +1s, 10 non-binding +1s, and 0 -1s the vote passes.
 
 Thanks for the help.
 
 On 9/7/12 2:56 PM, Bobby Evans bo...@apache.org wrote:
 
 I have built an RC0 for 0.23.3 and am calling a vote on it
 
 You can download the signed packages from:
 http://people.apache.org/~bobby/hadoop-0.23.3-candidate-0/
 
 It is tagged under svn at:
 https://svn.apache.org/repos/asf/hadoop/common/tags/release-0.23.3-rc0
 
 Please kick the tires and let me know if I missed anything, this is
 the first time I am doing a release.
 
 As per the bylaws the vote will be open for 7 days and will end Friday
 Sep 14th.
 
 I am a +1 (non-binding)
 
 --Bobby Evans
 

Re: svn branches cleanup

[Vinod Kumar Vavilapalli]

Seems like we are done with cleanup of 0.23.* and a separate email thread in 
progress on common-dev@h.a.o w.r.t 2.* branches.

Thanks for doing the needful, Owen!

+Vinod

On Aug 31, 2012, at 3:04 PM, Owen O'Malley wrote:

 On Fri, Aug 31, 2012 at 2:28 PM, Arun C Murthy a...@hortonworks.com wrote:
 
 
 On Aug 31, 2012, at 2:26 PM, Owen O'Malley wrote:
 
 We should rename the 2.x branches as:
 branch-2.0.1-alpha - branch-2.0
 branch-2.1.0-alpha - branch-2.1
 
 I'm ok with the rest, but please don't rename the 'alpha' branches. We'll 
 need those for later after hadoop-2 is stable.
 
 
 The pattern that we follow is that branches look like:
 
 --- trunk
\
 \-- branch-2.0
  \
   \- branch-2.1
\
 v
  branch-2
 
 With tags having the triples (2.0.0, 2.0.1). I was assuming that
 branch-2.0.1 was supposed to be branch-2.0. branch-2.0.1 only makes
 sense if your releases/tags are going to be 2.0.1.0.
 
 -- Owen

Re: Heads up: next hadoop-2 release

[Vinod Kumar Vavilapalli]

On Aug 31, 2012, at 9:45 AM, Arun C Murthy wrote:

 Makes sense. The only issue is rejiggering fix-versions, CHANGES.txt etc., 
 but I can do that.
 
 My plan to create the RC after 0.23.3 completes the test/integration cycle 
 it's currently in - should be done in the next week or so barring blockers.
 
 thanks,
 Arun


In which case shall we just wipe off 2.1.0-alpha for now and branch out only 
after 0.23.3's cycle is done. I don't expect major features to go in the 
meanwhile into branch-2 which we don't want in 2.1.0-alpha.

Thoughts?

Thanks,
+Vinod Kumar Vavilapalli
Hortonworks Inc.
http://hortonworks.com/



signature.asc
Description: Message signed with OpenPGP using GPGMail

Re: [VOTE] Maintain a single committer list for the Hadoop project

[Vinod Kumar Vavilapalli]

Given that a discussion of a TLP proposal is happening in parallel, and that 
there seems to be a positive response there, is this vote still happening?

At any rate, here's my opinion: The earlier project split, however painful it 
was, has done a lot of good, both in terms of project management as well as 
community focus. Leaving common project aside, merging the committer lists back 
is going to submerge the underlying issue of communities, that have acquired 
sufficient independence, attempting to function together and is also likely to 
make us depend on informal behavior of trusting someone to not commit code that 
they aren't really responsible for.

This is definitely going in the opposite direction of our long term goals.

-1.

Thanks,
+Vinod

Re: [DISCUSS] Spin out MR, HDFS and YARN as their own TLPs and disband Hadoop umbrella project

[Vinod Kumar Vavilapalli]

+1 for splitting the projects.

On Aug 30, 2012, at 6:24 PM, Chris Douglas wrote:

 The tasks that are simpler in a unified project- releases,
 cross-project patches, etc- are relatively rare, but all dev has paid
 a tax.

Agreed.

 That acknowledged, as Arun points out: the half-measures that
 have made the split painful can be fixed and enthusiasm/resources
 appear to be available for that. As long as TLPs are reconciled
 quickly and decisively, this can be successful. Without dedicated
 resources, we can expect the same result as before.


I am willing to volunteer myself to help with whatever it takes to accomplish 
this. Even the last time around, I did my bit to make the split happen, the 
fruits of which aren't all lost today.

Thanks,
+Vinod Kumar Vavilapalli
Hortonworks Inc.
http://hortonworks.com/

Re: svn branches cleanup

[Vinod Kumar Vavilapalli]

Thanks Bobby, makes sense to keep 0.23.3 as is for now.

What about my comments about 23.1 and 23.2?

Thanks,
+Vinod

On Aug 28, 2012, at 6:47 AM, Robert Evans wrote:

 I plan to do a RC of 0.23.3 in the next few days.  I am waiting for some
 tests of what is on branch-0.23 right now to pass before I create the
 branch.  MAPREDUCE-3943 went in recently and it is big enough I want some
 more tests before I feel comfortable with it.  The tests for it so far
 look good so I expect to get started on it today or tomorrow, but I have
 never done a release before so I am sure it will take me a few days to get
 everything right. Also I don't see any reason to branch early when all
 that is going in is bug fixes.
 
 --Bobby Evans
 
 
 On 8/27/12 8:55 PM, Vinod Kumar Vavilapalli vino...@hortonworks.com
 wrote:
 
 Seems to me that stale branches have started accumulating. Here's what I
 am thinking.
 
 2.* line
 - 2.0.1-alpha is released, so branch-2.0.1-alpha should instead be
 called branch-2.0.2-alpha?
 
 0.23.* line
 - 0.23.1 was released long time back, so knock off branch-0.23.1
 altogether?
 - 0.23.2 seems to be dead, so knock off branch-0.23.2 too?
 - 0.23.3 is the next expected release, so I suppose all the commits are
 going into branch-0.23. Either we can
   -- create branch-0.23.3 out of branch-0.23 now itself or
   -- commit as is to branch-0.23 and create RC out of the same whenever
 that happens.
 
 Thanks,
 +Vinod
 PS: I missed action for ~1 month, please correct me if I am wrong.
 

svn branches cleanup

[Vinod Kumar Vavilapalli]

Seems to me that stale branches have started accumulating. Here's what I am 
thinking.

2.* line
 - 2.0.1-alpha is released, so branch-2.0.1-alpha should instead be called 
branch-2.0.2-alpha?

0.23.* line
 - 0.23.1 was released long time back, so knock off branch-0.23.1 altogether?
 - 0.23.2 seems to be dead, so knock off branch-0.23.2 too?
 - 0.23.3 is the next expected release, so I suppose all the commits are going 
into branch-0.23. Either we can
-- create branch-0.23.3 out of branch-0.23 now itself or
-- commit as is to branch-0.23 and create RC out of the same whenever that 
happens.

Thanks,
+Vinod
PS: I missed action for ~1 month, please correct me if I am wrong.

Re: [VOTE] - Establish YARN as a sub-project of Apache Hadoop

[Vinod Kumar Vavilapalli]

On Aug 22, 2012, at 11:43 AM, Eli Collins wrote:

 On Wed, Aug 22, 2012 at 11:38 AM, Doug Cutting cutt...@apache.org wrote:
 2. Distinct MR, HDFS and YARN committers
 3. Combine MR, YARN, HDFS committers
 
 So we might better just vote on (2)
 versus (3)?
 
 Works for me.  What do others think?

Can you clarify more on what you are proposing we vote on?

What does (2) mean? Since (1) was dropped, does it mean we seed the YARN list 
with folks who have been contributing/reviewing patches on YARN?

Thanks,
+Vinod

Re: [VOTE] - Establish YARN as a sub-project of Apache Hadoop

[Vinod Kumar Vavilapalli]

Thanks for the clarification.

Seems like we can start a vote on those lines. But let's do that separately on 
a fresh thread. This one has stretched for far too long after the original vote 
thread concluded.

Thanks,
+Vinod

On Aug 23, 2012, at 11:33 AM, Eli Collins wrote:

 On Thu, Aug 23, 2012 at 11:13 AM, Vinod Kumar Vavilapalli
 vino...@hortonworks.com wrote:
 
 On Aug 22, 2012, at 11:43 AM, Eli Collins wrote:
 
 On Wed, Aug 22, 2012 at 11:38 AM, Doug Cutting cutt...@apache.org wrote:
 2. Distinct MR, HDFS and YARN committers
 3. Combine MR, YARN, HDFS committers
 
 So we might better just vote on (2)
 versus (3)?
 
 Works for me.  What do others think?
 
 Can you clarify more on what you are proposing we vote on?
 
 What does (2) mean?
 
 Distinct MR, HDFS and YARN committers means that MR, HDFS, and YARN
 each have their own set of committers. Today we have two sets (MR and
 HDFS) so under this option we would have three sets of committers.
 (And technically a 4th set which is the PMC which is shared across
 sub-projects and can commit to all of them).
 
 Since (1) was dropped, does it mean we seed the YARN list with folks who 
 have been contributing/reviewing patches on YARN?
 
 The vote would need to spell out how we would seed the YARN list. Per
 above I'd suggest seeding it with the current MR committers - ie the
 people who can commit to YARN today - there's no need to actively
 exclude people we already trust to commit to this code, and there's
 obvious downside to excluding them, for example, some patches need to
 span sub-projects (same reason all HDFS/MR committers can commit to
 Common).  If/when the sub-projects become TLPs (ie when there are real
 distinct boundaries between the projects) seems like a good time to
 divvy things up.
 
 Personally I'm in favor of #3, I liked Chris D's original proposal to
 just merge all the committer lists and call it a day!
 
 Thanks,
 Eli

Re: [VOTE] - Establish YARN as a sub-project of Apache Hadoop

[Vinod Kumar Vavilapalli]

+1, after the fact. Was off the grid.

Thanks,
+Vinod

On Jul 26, 2012, at 8:24 PM, Arun C Murthy wrote:

 As we discussed in the previous thread, I'd like to call a vote to establish 
 YARN as a sub-project (it's the best *term* we have to describe it in our 
 current nomenclature) of Apache Hadoop along with Common, HDFS  MapReduce.
 
 Specifically,
 # Create a separate top-level src folder hadoop-yarn, move it out of 
 hadoop-mapreduce-project in subversion at hadoop/common/trunk.
 # Create a separate YARN jira project and yarn-dev@ mailing-list.
 # Continue to co-release a single Hadoop release with Common, HDFS, YARN  
 MapReduce.
 
 Please vote, the vote will run the normal 7 days. Obviously, I'm +1.
 
 thanks,
 Arun
 

Re: Clarification about 2.* branches

[Vinod Kumar Vavilapalli]

I checked with Nicholas also who did the only merge into branch-2.0.0-alpha 
after the release and got a confirmation that I can delete the branch.

Removing the branch now.

Thanks,
+Vinod


On Jun 5, 2012, at 5:45 PM, Arun C Murthy wrote:

 +1 for blowing away branch-2.0.0-alpha now, we have the release tag if 
 necessary.
 
 thanks,
 Arun
 
 On Jun 5, 2012, at 4:40 PM, Vinod Kumar Vavilapalli wrote:
 
 Hi,
 
 I see two branches for 2.* now: branch-2 and branch-2.0.0-alpha and two 
 sections in CHANGES.txt: 2.0.1-alpha unreleased and 2.0.0-alpha released. It 
 is a little confusing, seems like branch-2.0.0-alpha was a staging branch 
 for the release and can be thrown away.
 
 Anyone committing patches to both branch-2 and branch-2.0.0-alpha? If not, 
 I'll blow away the later and rename the section in CHANGES.txt to branch-2.
 
 Thanks,
 +Vinod
 
 --
 Arun C. Murthy
 Hortonworks Inc.
 http://hortonworks.com/
 
 

Re: Clarification about 2.* branches

[Vinod Kumar Vavilapalli]

Not sure when it stopped being so, but we always created release tags for the 
releases and do away with the staging branches. I find it confusing as to which 
branches to commit to when we have dead branches lying around.

Regarding 0.23.*, you are right, I was about to send a separate email regarding 
those too.

Thanks,
+Vinod


On Jun 6, 2012, at 2:10 PM, Eli Collins wrote:

 Hey Vinod,
 
 Out of curiosity, why delete the branch?  Might make spelunking for
 svn revs that correspond to a release hard.  If we're deleting old
 release branches might as well delete the others (branch-0.23.0,
 branch-0.23.0-rc0, branch-0.23.1, branch-0.23.2, etc) as well?
 
 Thanks,
 Eli
 
 On Wed, Jun 6, 2012 at 1:52 PM, Vinod Kumar Vavilapalli
 vino...@hortonworks.com wrote:
 
 
 I checked with Nicholas also who did the only merge into branch-2.0.0-alpha 
 after the release and got a confirmation that I can delete the branch.
 
 Removing the branch now.
 
 Thanks,
 +Vinod
 
 
 On Jun 5, 2012, at 5:45 PM, Arun C Murthy wrote:
 
 +1 for blowing away branch-2.0.0-alpha now, we have the release tag if 
 necessary.
 
 thanks,
 Arun
 
 On Jun 5, 2012, at 4:40 PM, Vinod Kumar Vavilapalli wrote:
 
 Hi,
 
 I see two branches for 2.* now: branch-2 and branch-2.0.0-alpha and two 
 sections in CHANGES.txt: 2.0.1-alpha unreleased and 2.0.0-alpha released. 
 It is a little confusing, seems like branch-2.0.0-alpha was a staging 
 branch for the release and can be thrown away.
 
 Anyone committing patches to both branch-2 and branch-2.0.0-alpha? If not, 
 I'll blow away the later and rename the section in CHANGES.txt to branch-2.
 
 Thanks,
 +Vinod
 
 --
 Arun C. Murthy
 Hortonworks Inc.
 http://hortonworks.com/
 
 
 

Re: Clarification about 2.* branches

[Vinod Kumar Vavilapalli]

Done with deletion of the staging branch. Also updated all CHANGES.txt to point 
to a running branch-2 instead of a release. When we decide to make a release 
branch, we can separate sections then.

Thanks,
+vinod


On Jun 5, 2012, at 4:40 PM, Vinod Kumar Vavilapalli wrote:

 Hi,
 
 I see two branches for 2.* now: branch-2 and branch-2.0.0-alpha and two 
 sections in CHANGES.txt: 2.0.1-alpha unreleased and 2.0.0-alpha released. It 
 is a little confusing, seems like branch-2.0.0-alpha was a staging branch for 
 the release and can be thrown away.
 
 Anyone committing patches to both branch-2 and branch-2.0.0-alpha? If not, 
 I'll blow away the later and rename the section in CHANGES.txt to branch-2.
 
 Thanks,
 +Vinod

Clarification about 2.* branches

[Vinod Kumar Vavilapalli]

Hi,

I see two branches for 2.* now: branch-2 and branch-2.0.0-alpha and two 
sections in CHANGES.txt: 2.0.1-alpha unreleased and 2.0.0-alpha released. It is 
a little confusing, seems like branch-2.0.0-alpha was a staging branch for the 
release and can be thrown away.

Anyone committing patches to both branch-2 and branch-2.0.0-alpha? If not, I'll 
blow away the later and rename the section in CHANGES.txt to branch-2.

Thanks,
+Vinod

Re: [DISCUSS] branch-0.23 is dead, long live branch-0.23

[Vinod Kumar Vavilapalli]

+1 for leaving 0.23.2 as branch-0.23 for the short term, while branch-0.2 
stabilizes in parallel.

Thanks,
+Vinod


On Apr 2, 2012, at 8:15 AM, Robert Evans wrote:

 At Yahoo we have been running hadoop-0.23.2 in an effort to stabilize it and
 validate it with our internal customers.  I propose that we don¹t completely
 kill off branch-0.23 just yet so that we can finish up this effort and make
 some small sustaining releases (e.g. 0.23.3).  At the same time we are
 starting to use hadoop-2 (with HDFS HA, HDFS-PB ...) as a second train.
 
 As such, I volunteer to take over release management of branch-0.23.  Of
 course I will treat branch 0.23 as a stabilizing line off of 2.0 and not
 accept anything in that is not first in branch-2 and trunk.   Essentially,
 this is something that we have to do either internally or publicly, and I
 would much rather do this publicly.
 
 --Bobby Evans
 

Re: [VOTE] Rename hadoop branches post hadoop-1.x

[Vinod Kumar Vavilapalli]

My preference: 3, 4, 2, 1. (binding)

Thanks
+Vinod


On Mar 19, 2012, at 6:06 PM, Arun C Murthy wrote:

 We've discussed several options:
 
 (1) Rename branch-0.22 to branch-2, rename branch-0.23 to branch-3.
 (2) Rename branch-0.23 to branch-3, keep branch-0.22 as-is i.e. leave a hole.
 (3) Rename branch-0.23 to branch-2, keep branch-0.22 as-is.
 (4) If security is fixed in branch-0.22 within a short time-frame i.e. 2 
 months then we get option 1, else we get option 3. Effectively postpone 
 discussion by 2 months, start a timer now. 
 (5) Do nothing, keep branch-0.22 and branch-0.23 as-is.
 
 Let's do a STV [1] to get reach consensus.
 
 Please vote by listing the options above in order of your preferences.
 
 My vote is 3, 4, 2, 1, 5 in order (binding).
 
 The vote will run the normal 7 days.
 
 thanks,
 Arun
 
 [1] http://en.wikipedia.org/wiki/Single_transferable_vote
 

Re: [RESULT]: [VOTE] Release Apache Hadoop 0.23.1-rc2

[Vinod Kumar Vavilapalli]

Done updating the site. Changes should be visible in some time.

@Arun,
  Haven't done the jdiffs. Dunno how to do in the maven world.
  Haven't done the mvn publish stuff too. If you haven't already, please
also make sure that the mvn jars are published with the correct version.

Thanks,
+Vinod


On Mon, Feb 27, 2012 at 10:38 PM, Vinod Kumar Vavilapalli 
vino...@hortonworks.com wrote:


 Updating the release bits now.

 +Vinod


 On Mon, Feb 27, 2012 at 12:29 PM, Arun C Murthy a...@hortonworks.comwrote:

 With 7 +1s (4 binding), one -0 and one -1 (0 binding), the vote passes.

 Thanks to all who voted, I'll push out the release.

 Arun

 On Feb 17, 2012, at 11:23 PM, Arun C Murthy wrote:

  I've created another release candidate for hadoop-0.23.1 that I would
 like to release.
 
  It is available at:
 http://people.apache.org/~acmurthy/hadoop-0.23.1-rc2/
  The hadoop-0.23.1-rc2 svn tag:
 https://svn.apache.org/repos/asf/hadoop/common/tags/release-0.23.1-rc2
  The maven artifacts for hadoop-0.23.1-rc2 are also available at
 repository.apache.org.
 
  Please try the release and vote; the vote will run for the usual 7 days.
 
  thanks,
  Arun

 --
 Arun C. Murthy
 Hortonworks Inc.
 http://hortonworks.com/

Re: [RESULT]: [VOTE] Release Apache Hadoop 0.23.1-rc2

[Vinod Kumar Vavilapalli]

Updating the release bits now.

+Vinod


On Mon, Feb 27, 2012 at 12:29 PM, Arun C Murthy a...@hortonworks.com wrote:

 With 7 +1s (4 binding), one -0 and one -1 (0 binding), the vote passes.

 Thanks to all who voted, I'll push out the release.

 Arun

 On Feb 17, 2012, at 11:23 PM, Arun C Murthy wrote:

  I've created another release candidate for hadoop-0.23.1 that I would
 like to release.
 
  It is available at:
 http://people.apache.org/~acmurthy/hadoop-0.23.1-rc2/
  The hadoop-0.23.1-rc2 svn tag:
 https://svn.apache.org/repos/asf/hadoop/common/tags/release-0.23.1-rc2
  The maven artifacts for hadoop-0.23.1-rc2 are also available at
 repository.apache.org.
 
  Please try the release and vote; the vote will run for the usual 7 days.
 
  thanks,
  Arun

 --
 Arun C. Murthy
 Hortonworks Inc.
 http://hortonworks.com/

Re: [VOTE] Release Apache Hadoop 0.23.1-rc2

[Vinod Kumar Vavilapalli]

I checked this RC, based on the same check-list as RC1:

 - Signatures, message digests, the top level full LICENSE.txt,
NOTICE.txt and README.txt for both the source and binary artifacts are
all good. CHANGES.txt for common, hdfs and mapped are correctly
located like before.
 - Able to build the tars out of the source tar ball.

Testing: All testing on single node, unsecured, default mode. All
under 10 minutes :)
  - Started HDFS daemons successfully , created directories.
  - Successfully started YARN daemons - ResourceManager and
NodeManager and mapred history server.
  - Ran wordcount, pi, random writer, sort, grep and they all pass.

+1 for the latest RC, it's time we push this out!!

Thanks,
+Vinod

On Fri, Feb 17, 2012 at 11:23 PM, Arun C Murthy a...@hortonworks.com wrote:
 I've created another release candidate for hadoop-0.23.1 that I would like to 
 release.

 It is available at: http://people.apache.org/~acmurthy/hadoop-0.23.1-rc2/
 The hadoop-0.23.1-rc2 svn tag: 
 https://svn.apache.org/repos/asf/hadoop/common/tags/release-0.23.1-rc2
 The maven artifacts for hadoop-0.23.1-rc2 are also available at 
 repository.apache.org.

 Please try the release and vote; the vote will run for the usual 7 days.

 thanks,
 Arun

 --
 Arun C. Murthy
 Hortonworks Inc.
 http://hortonworks.com/

Re: [VOTE] Release Apache Hadoop 0.23.1-rc2

[Vinod Kumar Vavilapalli]

Roman,

you are compiling on 64 bit machines?

 not only make it impossible to build the right version
 of container executor without hand-editing the pom.xml,

The idea was to have 32 bit binary all the time, can you let us know
what issue you are facing. During the build itself?

 but also make it impossible to deploy the secure
 version of hadoop without additional burden of installing
 32bit legacy support on all the slave nodes.

Again, what do you mean by this? You mean you will have to install all
32 bit dependencies that the container-executor may have on all nodes?
AFAIU, if you have a single 32bit lib/binary on a 64 bit machine, you
don't need any other 32bit lib dependencies. Please correct me if I am
wrong. Myself cannot test it exactly like the way you are testing as I
don't have access to nodes which don't have 32bits installed, so more
specific details are helpful.

Thanks,
+Vinod

Re: [VOTE] Release Apache Hadoop 0.23.1-rc2

[Vinod Kumar Vavilapalli]

Todd,

From your analysis at HDFS-2991, looks like this was there in 0.23
too. Also, seems this happens only at scale, and only (paraphrasing
you) when the file is reopened for append on an exact block
boundary.

Agree it is a critical fix, but given above, can we proceed along with
0.23.1? Anyways, 0.23.1 is still an alpha (albeit of next level), so
I'd think we can get that in for 0.23.2.

+Vinod

On Wed, Feb 22, 2012 at 6:43 PM, Todd Lipcon t...@cloudera.com wrote:
 -1, unfortunately. HDFS-2991 is a blocker regression introduced in
 0.23.1. See the JIRA for instructions on how to reproduce on the rc2
 build.

 -Todd

 On Fri, Feb 17, 2012 at 11:23 PM, Arun C Murthy a...@hortonworks.com wrote:
 I've created another release candidate for hadoop-0.23.1 that I would like 
 to release.

 It is available at: http://people.apache.org/~acmurthy/hadoop-0.23.1-rc2/
 The hadoop-0.23.1-rc2 svn tag: 
 https://svn.apache.org/repos/asf/hadoop/common/tags/release-0.23.1-rc2
 The maven artifacts for hadoop-0.23.1-rc2 are also available at 
 repository.apache.org.

 Please try the release and vote; the vote will run for the usual 7 days.

 thanks,
 Arun

 --
 Arun C. Murthy
 Hortonworks Inc.
 http://hortonworks.com/





 --
 Todd Lipcon
 Software Engineer, Cloudera

Re: [VOTE] Release Apache Hadoop 0.23.1-rc1

[Vinod Kumar Vavilapalli]

I checked this RC, based on my check-list:

 - Signatures and message digests all are good.
 - The top level full LICENSE, NOTICE and README for both the source and
binary artifacts are good
 - CHANGES.txt for common, hdfs and mapped are correctly located.
 - Able to build the tars out of the source tar ball.

Testing: All testing on single node, unsecured, default mode.
  - Started HDFS daemons successfully , created directories.
  - Successfully started YARN daemons - ResourceManager and NodeManager
  - Successfully started mapred history server.
  - Ran wordcount, pi, random writer, sort, grep and they all pass just
fine.

Even before the RC, been actively doing performance benchmarking and
testing on big clusters with this code. 0.23.1 clearly has much more
improvements compared to 0.23., even though it is still (the next level)
alpha.

With that, here's my +1 for the latest RC.

Thanks,
+Vinod

On Tue, Feb 14, 2012 at 9:28 PM, Arun C Murthy a...@hortonworks.com wrote:

 I've created another release candidate for hadoop-0.23.1 that I would like
 to release.

 It is available at: http://people.apache.org/~acmurthy/hadoop-0.23.1-rc1/
 The hadoop-0.23.1-rc1 svn tag:
 https://svn.apache.org/repos/asf/hadoop/common/tags/release-0.23.1-rc1
 The maven artifacts for hadoop-0.23.1-rc1 are also available at
 repository.apache.org.

 Since hadoop-0.23.1-rc0 last week, we've fixed some important bugs:
 # HDFS-2923. Namenode IPC handler count uses the wrong configuration key.
 # MAPREDUCE-3858. Task attempt failure during commit results in task never
 completing.
 # MAPREDUCE-3846. Addressed MR AM hanging issues during AM restart and
 then the recovery.

 Please try the release and vote; the vote will run for the usual 7 days.

 thanks,
 Arun

 --
 Arun C. Murthy
 Hortonworks Inc.
 http://hortonworks.com/

Re: [VOTE] Release hadoop-0.23.0-rc1

[Vinod Kumar Vavilapalli]

Thanks for the update, Arun!

I checked this RC:

 - Signatures and message digests all are good.
 - We still need a top level full LICENSE, NOTICE and a README for both the
source and binary artifacts. [can be copied from
http://svn.apache.org/repos/asf/hadoop/common/tags/release-0.20.205.0-rc1/]
 - CHANGES.txt for common and hdfs are duplicated in
./share/doc/hadoop/$PROJECT and
./share/doc/hadoop/hadoop-project-dist/$PREOJECT
 - CHANGES.txt files are still a bit hard to find. Top level would be good,
but then we will need to rename them as COMMON-CHANGES.txt etc. What do you
and others think?
 - What about Release-notes? It will be great to package them. Not sure if
we ever shipped release-notes out with the release though.

Testing: Did the same tests that I did with RC0, on a single node.
  - Started HDFS daemons in secure mode running as 'hdfs' user, created
directories.
  - Successfully started YARN daemons - ResourceManager and NodeManager -
running as 'mapred' user.
  - Still running into the same issue running mapreduce jobs using the
container-executor binary shipped with the tar-ball:
2011-11-01 16:30:00,326 INFO
org.apache.hadoop.yarn.server.nodemanager.containermanager.localizer.ResourceLocalizationService:
Localizer failed
java.io.IOException: App initialization failed (2)
 I tried installing and testing trunk, 0.23 code and the current RC,
was a lengthy affair. Finally I cornered this to the built binary. The
container-executor binary shipped is a 64 bit version, while I am on a
32-bit arch. When I manually built the code myself and replaced just the
binary with my 32 bit version one, everything went fine. I guess we need to
ship both the versions?
  - With the replaced binary, I ran wordcount, pi, sort, grep as a user
different from hdfs/mapred and they all pass just fine.

Thanks,
+Vinod

On Wed, Nov 2, 2011 at 7:12 AM, Arun C Murthy a...@hortonworks.com wrote:

 I've created a new release candidate (rc1) for hadoop-0.23.0 that I would
 like to release.
 http://people.apache.org/~acmurthy/hadoop-0.23.0-rc1/

 Please try the release and vote; the vote will run for the usual 7 days.

 thanks,
 Arun

Re: [VOTE] Release hadoop-0.23.0-rc0

[Vinod Kumar Vavilapalli]

I downloaded the bits. Verified the signatures.

Started HDFS daemons in secure mode running as 'hdfs' user, created
directories. Successfully started YARN daemons - ResourceManager and
NodeManager - running as 'mapred' user.

But I am running into an issue while running mapreduce jobs using the
container-executor binary shipped with the tar-ball.

2011-11-01 16:30:00,326 WARN
org.apache.hadoop.yarn.server.nodemanager.LinuxContainerExecutor: Exit code
from container is : 2
2011-11-01 16:30:00,326 INFO
org.apache.hadoop.yarn.server.nodemanager.ContainerExecutor:
2011-11-01 16:30:00,326 INFO
org.apache.hadoop.yarn.server.nodemanager.containermanager.localizer.ResourceLocalizationService:
Localizer failed
java.io.IOException: App initialization failed (2)
at
org.apache.hadoop.yarn.server.nodemanager.LinuxContainerExecutor.startLocalizer(LinuxContainerExecutor.java:147)
at
org.apache.hadoop.yarn.server.nodemanager.containermanager.localizer.ResourceLocalizationService$LocalizerRunner.run(ResourceLocalizationService.java:859)
Caused by: org.apache.hadoop.util.Shell$ExitCodeException:
/home/vinodkv/Downloads/hadoop-0.23.0/bin/../bin/container-executor: 1:
Syntax error: Unterminated quoted string

at org.apache.hadoop.util.Shell.runCommand(Shell.java:261)
at org.apache.hadoop.util.Shell.run(Shell.java:188)
at
org.apache.hadoop.util.Shell$ShellCommandExecutor.execute(Shell.java:381)
at
org.apache.hadoop.yarn.server.nodemanager.LinuxContainerExecutor.startLocalizer(LinuxContainerExecutor.java:139)
... 1 more

Still debugging to see if it is an environment issue.

Thanks,
+Vinod


On Tue, Nov 1, 2011 at 3:17 PM, Arun C Murthy a...@hortonworks.com wrote:

 I've created a release candidate for hadoop-0.23.0 that I would like to
 release.

 It is available at: http://people.apache.org/~acmurthy/hadoop-0.23.0-rc0/

 hadoop-0.23 has significant new features: HDFS Federation and NextGen
 MapReduce being the highlights.

 It's also very early in the 0.23 life-cycle and the release is distinctly
 'alpha' quality and is not intended to be stable release right-away. The
 plan is to deploy this to smallish (500+ nodes) clusters and to start
 hardening it. This should also help downstream projects (Pig, Hive, HBase)
 start testing against the 0.23 line. Expect to see more bug-fix releases of
 the branch-0.23 in the forthcoming weeks (0.23.1 etc.)

 Please try the release and vote; the vote will run for the usual 7 days.

 thanks,
 Arun