Re: [ANNOUNCE] New Apache Hadoop PMC: Vrushali Channapattan
Congratulations, Vrushali! Jason On Mon, Jul 30, 2018 at 9:53 PM, Rohith Sharma K S < rohithsharm...@apache.org> wrote: > Hi All, > > It is my pleasure to announce that the Apache Hadoop PMC voted to add > Vrushali Channapattan as a PMC member. This is in recognition of > Vrushali's > contributions to the Hadoop community. > > Please join me in congratulating Vrushali! > > Regards, > Rohith Sharma K S >
CVE-2017-15713: Apache Hadoop MapReduce job history server vulnerability
CVE-2017-15713: Apache Hadoop MapReduce job history server vulnerability Severity: Severe Vendor: The Apache Software Foundation Versions Affected: Hadoop 0.23.0 to 0.23.11 Hadoop 2.0.0-alpha to 2.8.2 Hadoop 3.0.0-alpha to 3.0.0-beta1 Users affected: Users running the MapReduce job history server daemon Impact: Vulnerability allows a cluster user to expose private files owned by the user running the MapReduce job history server process. The malicious user can construct a configuration file containing XML directives that reference sensitive files on the MapReduce job history server host. Mitigation: Users should upgrade to Apache Hadoop 2.7.5, 2.8.3, 2.9.0, or 3.0.0. Credit: This issue was discovered by Man Yue Mo of lgtm.com - To unsubscribe, e-mail: general-unsubscr...@hadoop.apache.org For additional commands, e-mail: general-h...@hadoop.apache.org
[ANNOUNCE] Eric Payne added to the Apache Hadoop PMC
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
Re: [ANNOUNCE] New Hadoop Committer - Varun Saxena
Congratulations, Varun! Jason From: 俊平堵 To: general@hadoop.apache.org Cc: varunsax...@apache.org Sent: Friday, June 24, 2016 1:51 PM Subject: [ANNOUNCE] New Hadoop Committer - Varun Saxena On behalf of the Apache Hadoop PMC, I am pleased to announce that Varun Saxena has been elected a committer on the Apache Hadoop project. We appreciate all of Varun's hard work thus far, and we look forward to his continued contributions. Congratulations, Varun! Cheers, Junping
Re: [ANNOUNCE] New Hadoop Committer - Naganarasimha Garla
Congratulations! Jason From: Wangda Tan To: general@hadoop.apache.org; Naganarasimha Garla Sent: Thursday, April 7, 2016 12:59 PM Subject: [ANNOUNCE] New Hadoop Committer - Naganarasimha Garla 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 - Li Lu
Congratulations, Li! Jason From: Junping Du To: General Cc: Li Lu Sent: Monday, February 22, 2016 4:23 PM Subject: [ANNOUNCE] New Hadoop Committer - Li Lu On behalf of the Apache Hadoop PMC, I am pleased to announce that Li Lu has been elected a committer on the Apache Hadoop project. We appreciate all of Li's hard work thus far, and we look forward to his continued contributions. Welcome onboard and congratulations, Li! Thanks, Junping?
[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
Re: [ANNOUNCE] New Hadoop Committer - Sangjin Lee
Congratulations, Sangjin! Jason From: Ming Ma To: general@hadoop.apache.org Cc: Sangjin Lee Sent: Wednesday, September 30, 2015 7:34 PM Subject: Re: [ANNOUNCE] New Hadoop Committer - Sangjin Lee Congrats Sangjin! On Wed, Sep 30, 2015 at 5:17 PM, Karthik Kambatla wrote: > [bcc: general@, please bcc: (and not cc:) general@ if you want to include] > > On behalf of the Apache Hadoop PMC, I am very pleased to announce that > Sanjin Lee has been elected a committer on the Apache Hadoop project > recognizing his continued contributions to the project. > > Sangjin is already a branch committer on YARN-2928 and can hit the ground > running :) > > Welcome Sangjin! > > Cheers! >
Re: [ANNOUNCE] New Hadoop Committer - Anubhav dhoot
Congratulations, Anubhav! Jason From: Karthik Kambatla To: Anubhav Dhoot Sent: Sunday, September 20, 2015 9:56 PM Subject: [ANNOUNCE] New Hadoop Committer - Anubhav dhoot On behalf of the Apache Hadoop PMC, I am pleased to announce that Anubhav Dhoot has been elected a committer on the Apache Hadoop project recognizing his contributions to the project. We appreciate Anubhav's hard work thus far, and and look forward to his contributions. Welcome Anubhav! Cheers!
Re: [ANNOUNCE] New Hadoop committer - Zhihai Xu
Congratulations, Zhihai! Jason From: Karthik Kambatla To: Zhihai Xu Sent: Thursday, July 30, 2015 2:36 PM Subject: [ANNOUNCE] New Hadoop committer - Zhihai Xu 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] New Hadoop Committer - Ming Ma
Congratulations, Ming! Jason From: Chris Nauroth To: "general@hadoop.apache.org" Sent: Thursday, June 18, 2015 2:55 PM Subject: [ANNOUNCE] New Hadoop Committer - Ming Ma On behalf of the Apache Hadoop PMC, I am pleased to announce that Ming Ma has been elected as a committer on the Apache Hadoop project. We appreciate all of Ming's hard work thus far, and we look forward to his continued contributions. Welcome, Ming! --Chris Nauroth
Re: [ANNOUNCE] Welcoming Jian He to Apache Hadoop PMC
Congratulations, Jian! Jason From: Vinod Kumar Vavilapalli To: general@hadoop.apache.org Cc: jianhe...@gmail.com Sent: Monday, January 5, 2015 5:51 PM Subject: [ANNOUNCE] Welcoming Jian He to Apache Hadoop PMC 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
Re: [ANNOUNCE] Welcoming Zhijie Shen to Apache Hadoop PMC
Congratulations, Zhijie! Jason From: Vinod Kumar Vavilapalli To: general@hadoop.apache.org Cc: Zhijie Shen Sent: Monday, January 5, 2015 5:51 PM Subject: [ANNOUNCE] Welcoming Zhijie Shen to Apache Hadoop PMC 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
Re: [ANNOUNCE] New Hadoop Committers - Akira Ajisaka and Tsuyoshi Ozawa
Congratulations Akira and Tsuyoshi! Jason From: Steve Loughran To: general@hadoop.apache.org Sent: Wednesday, December 17, 2014 9:55 AM Subject: [ANNOUNCE] New Hadoop Committers - Akira Ajisaka and Tsuyoshi Ozawa 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.
Re: [ANNOUNCE] New Hadoop Committer - Carlo Curino
Congratulations, Carlo!Jason From: Chris Douglas To: "general@hadoop.apache.org" Sent: Friday, December 5, 2014 2:43 PM Subject: [ANNOUNCE] New Hadoop Committer - Carlo Curino On behalf of the Apache Hadoop PMC, I'm pleased to announce (albeit belatedly) that Carlo Curino has been elected as a committer on the project. Congratulations Carlo; thank you for all your contributions to Hadoop! -C
Re: [ANNOUNCE] New Hadoop Committers - Gera Shegalov and Robert Kanter
Congratulations, Gera and Robert! Jason From: Sandy Ryza To: general@hadoop.apache.org Sent: Thursday, December 4, 2014 1:56 PM Subject: [ANNOUNCE] New Hadoop Committers - Gera Shegalov and Robert Kanter On behalf of the Apache Hadoop PMC, I am pleased to announce that Gera Shegalov and Robert Kanter 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, Gera and Robert! -Sandy
Re: [ANNOUNCE] New Hadoop Committer - Xuan Gong
Congratulations, Xuan! Jason On 04/13/2014 07:49 PM, Vinod Kumar Vavilapalli wrote: 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
Re: [ANNOUNCE] New Hadoop Committer - Ravi Prakash
Congratulations, Ravi! Jason On 12/09/2013 01:08 PM, Vinod Kumar Vavilapalli wrote: 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
Re: [VOTE] change bylaws to add "branch committers"
+1 (binding)
On 07/25/2013 01:38 PM, Chris Douglas 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.
+Significant, 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.
+
All Apache committers are required to have a signed Contributor
License Agreement (CLA) on file with the Apache Software
Foundation. There is a
+ Lazy Consensus -
+ Lazy consensus requires no -1 votes ('silence gives assent').
+
Lazy Majority -
A lazy majority vote requires 3 binding +1
votes and more binding +1 votes than -1 votes.
@@ -279,6 +289,12 @@
Lazy 2/3 majority of PMC members
+ New Branch Committer
+
+When a branch committer is proposed for the PMC
+
+Lazy consensus of active PMC members
+
New Committer
When a new committer is proposed for the project
@@ -291,6 +307,13 @@
Consensus approval of active PMC members
+ Branch Committer Removal
+
+When removal of commit privileges is sought or
+ when the branch is merged to the mainline
+
+Lazy 2/3 majority of active PMC members
+
Committer Removal
When removal of commit privileges is sought. Note: Such
Re: [VOTE] sed bylaws.html -e 's/lazy\s+consensus/consensus approval/gi'
+1 (binding) Jason On 03/25/2013 01:28 PM, Robert Evans wrote: As per Aaron's request I am starting a new voting thread to make it obvious that there is a vote happening. I propose that we change the term "lazy consensus" to "consensus approval" (aka s/lazy\s+consensus/consensus approval/gi) in the bylaws so that it matches the terms used in the apache foundation glossary. No actual change to our voting would take place, just the term we use to describe that voting. As per the by-laws this would take a "lazy majority" of active PMC members (although others are encouraged to speak up). Lazy Majority - A lazy majority vote requires 3 binding +1 votes and more binding +1 votes than -1 votes. Voting lasts 7 days, so it closes Monday April 1st (But this is not a joke). I am +1 (binding) --Bobby
Re: [VOTE] hadoop 0.23.6 rc1 release
+1 (non-binding) - Verified signatures and checksums - Built from source, deployed pseudo-distributed cluster and ran some example jobs successfully - Deployed pseudo-distributed cluster from binary tarball and ran some example jobs successfully Note that during testing I discovered the web proxy server doesn't startup successfully due to a missing directory and filed YARN-363. I'm not considering that a blocker since the missing directory can be created manually or the user can run the web proxy as part of the RM as a workaround. Jason On 01/29/2013 08:29 AM, Thomas Graves wrote: I've created another release candidate (RC1) for hadoop-0.23.6 that I would like to release. This release is a sustaining release with several important bug fixes in it. It also contains fixes for the issues found in rc0 - YARN-354, HDFS-4426, and HADOOP-9255 The RC is available at: http://people.apache.org/~tgraves/hadoop-0.23.6-candidate-1/ The RC tag in svn is here: http://svn.apache.org/viewvc/hadoop/common/tags/release-0.23.6-rc1/ 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, Tom Graves
Re: [VOTE] hadoop 0.23.6 release
We will want to pull in the fix for YARN-354 as well, since it's the same type of issue with the WebAppProxyServer. Jason On 01/23/2013 08:53 AM, Jason Lowe wrote: I filed HDFS-4426 when I ran across the issue checking out the release candidate. It's currently in Patch Available, and it looks close to being committed. Jason On 01/23/2013 08:48 AM, Thomas Graves wrote: Thanks Daryn, is there a fix for that otherwise perhaps I'll just revert that change. Tom On 1/22/13 1:52 PM, "Daryn Sharp" wrote: -1, secondary namenode won't stay up due after HADOOP-9181. The 2NN's main fires off a daemon thread and relied on the http server not running as a daemon, so the 2NN exits immediately.
Re: [VOTE] hadoop 0.23.6 release
I filed HDFS-4426 when I ran across the issue checking out the release candidate. It's currently in Patch Available, and it looks close to being committed. Jason On 01/23/2013 08:48 AM, Thomas Graves wrote: Thanks Daryn, is there a fix for that otherwise perhaps I'll just revert that change. Tom On 1/22/13 1:52 PM, "Daryn Sharp" wrote: -1, secondary namenode won't stay up due after HADOOP-9181. The 2NN's main fires off a daemon thread and relied on the http server not running as a daemon, so the 2NN exits immediately.
Re: [VOTE] hadoop 0.23.5 release
- Verified signatures and digests on src and dist tarballs - Verified src tarball builds successfully - Successfully setup a single-node cluster and ran some simple jobs +1 (non-binding) On 11/20/2012 01:24 PM, Thomas Graves wrote: I've created a release candidate (RC0) for hadoop-0.23.5 that I would like to release. This release is a sustaining release with several important bug fixes in it. The RC is available at: http://people.apache.org/~tgraves/hadoop-0.23.5-candidate-0/ The RC tag in svn is here: http://svn.apache.org/viewvc/hadoop/common/tags/release-0.23.5-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, Tom Graves
Re: [VOTE] Release hadoop-2.0.2-alpha
+1 (non-binding) - Verified signatures and digests on dist and src tarballs - Setup single-node, pseudo-distributed cluster without security - Ran a sleep job successfully and checked the history via the historyserver Jason On 10/01/2012 10: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/
Re: [VOTE] 0.23.4 release
I think HADOOP-8310 should also be added, as we've seen issues with the AM's web UI related to FileContext#checkPath. Jason On 10/01/2012 03:42 PM, Robert Evans wrote: OK, I'll spin an RC with those changes in it. On 10/1/12 3:35 PM, "Arun C Murthy" wrote: If you think 0.23.5 is a month or so away, I'd encourage you to pull it in right-away... this will ensure anyone external using this will get a good out-of-box experience. thanks, Arun On Oct 1, 2012, at 6:48 AM, Robert Evans wrote: I think I would prefer to merge them onto branch-0.23 and have them come out as part of 0.23.5. It will probably show up in a month or so, as we expect to find more issues as Yahoo! deploys this to more and larger clusters. If you really feel strongly about it I am OK with merging it in, I just don't see a critical need for it right now. --Bobby On 9/30/12 4:28 PM, "Arun C Murthy" wrote: Hey Bobby, Thanks for getting this RC out. You might want to pull in YARN-137 and YARN-138 into this too. thanks, Arun On Sep 29, 2012, at 8:35 AM, Robert Evans wrote: I have built a 0.23.4-rc0 and am calling a release vote on it. As per the bylaws this vote will be open for 1 week, and will close next Saturday October 6th. You can access the release through the apache maven staging repo, with the 0.23.4-rc0 tag in subversion, and at http://people.apache.org/~bobby/hadoop-0.23.4-candidate-0/ This release is a sustaining release with several important bug fixes in it. Most notably upgrading of a 1.0 cluster with append/sync enabled should now work (HDFS-3731). There are no known blockers against this release, there are only two critical issues. HADOOP-8811 Compile hadoop native library in FreeBSD HDFS-3990 NN's health report has severe performance problems HDFS-3990 only really has a significant impact on large clusters, and can be mitigated by enabling DNS caching. I have run several manual tests on this release on a small insecure cluster and all of them pass I am a +1 (binding) for this release. On a side note I am happy to announce that the 0.23 line is being rolled out more widely at Yahoo!. We just installed 0.23.3 on a 2000 node cluster and have only seen a few issues (HDFS-3990 is the biggest of them). I expect to do a 0.23.5 release in the coming weeks/months as we find more issues running on large clusters. --Bobby Evans -- Arun C. Murthy Hortonworks Inc. http://hortonworks.com/ -- Arun C. Murthy Hortonworks Inc. http://hortonworks.com/
Re: [VOTE] 0.23.3 release
+1 (non-binding) - Verified checksums and signatures. - Verified source is buildable including native. - Ran sleep and wordcount jobs on a single-node, insecure cluster. Jason On 09/07/2012 02:56 PM, Bobby Evans 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: [VOTE] - Establish YARN as a sub-project of Apache Hadoop
I think this was being done via HADOOP-8652, but it looks like there were some issues updating the site after the commit. I'm assuming they're still working through those issues. Jason On 08/13/2012 09:16 AM, Thomas Graves wrote: Can we update the mailing list page with the new ones and combined users: http://hadoop.apache.org/mailing_lists.html? Thanks Tom On 8/8/12 2:29 PM, "Arun C Murthy" wrote: Ok, we are nearly there. # The new YARN jira is functional now (albeit with some teething issues with notifications/workflow which should be resolved soon): https://issues.apache.org/jira/browse/YARN # I've committed YARN-1 to move YARN out of hadoop-mapreduce-project onto hadoop-yarn-project in subversion. # The yarn-dev@ mailing list is active. # All jira notifications are going to yarn-issues@ and all subversion commit notifications are going to yarn-commits@. Please do subscribe to the relevant mailing lists. Also note that there is *no* yarn-user@ list since all user interactions are now via u...@hadoop.apache.org. If you see issues, please let me know and I'll try to respond ASAP. thanks, Arun On Aug 3, 2012, at 12:51 AM, Arun C Murthy wrote: With 22 +1s (9 binding) and no -1s the vote passes unanimously. Thanks to all who voted. I'll start the necessary process to move on this. thanks, Arun 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 -- Arun C. Murthy Hortonworks Inc. http://hortonworks.com/ -- Arun C. Murthy Hortonworks Inc. http://hortonworks.com/
Re: [VOTE] Rename hadoop branches post hadoop-1.x
3, 2, 1, 4, 5 (non-binding) Jason On 03/19/2012 08: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
