Re: [VOTE] Release 0.20.204.0-rc0
Hi all, I've just run unit test of 0.20.204 using SUN jdk1.6.0_21, on a 64bit RHEL machine, and find the following cases failed: [junit] Test org.apache.hadoop.mapred.TestJobTrackerRestart FAILED (timeout) [junit] Test org.apache.hadoop.mapred.TestJobTrackerRestartWithLostTracker FAILED [junit] Test org.apache.hadoop.mapred.TestJobTrackerSafeMode FAILED [junit] Test org.apache.hadoop.filecache.TestMRWithDistributedCache FAILED [junit] Test org.apache.hadoop.filecache.TestTrackerDistributedCacheManager FAILED [junit] Test org.apache.hadoop.mapred.TestMiniMRMapRedDebugScript FAILED [junit] Test org.apache.hadoop.mapred.TestRecoveryManager FAILED [junit] Test org.apache.hadoop.mapred.TestTaskTrackerLocalization FAILED [junit] Test org.apache.hadoop.mapred.TestJobTrackerRestartWithCS FAILED (timeout) [junit] Test org.apache.hadoop.mapred.TestRackAwareTaskPlacement FAILED I run each failed test case for 4 times, the above 9 cases failed for each round, while the last case succeeded twice and failed twice. I also tested 0.20.203 rc1 with the same testing environment some time earlier, and got almost the same result(with the failed cases attached below) [junit] Test org.apache.hadoop.mapred.TestJobTrackerRestart FAILED [junit] Test org.apache.hadoop.mapred.TestJobTrackerRestartWithLostTracker FAILED [junit] Test org.apache.hadoop.mapred.TestJobTrackerSafeMode FAILED [junit] Test org.apache.hadoop.filecache.TestMRWithDistributedCache FAILED [junit] Test org.apache.hadoop.filecache.TestTrackerDistributedCacheManager FAILED [junit] Test org.apache.hadoop.mapred.TestMiniMRMapRedDebugScript FAILED [junit] Test org.apache.hadoop.mapred.TestRecoveryManager FAILED [junit] Test org.apache.hadoop.mapred.TestTaskTrackerLocalization FAILED [junit] Test org.apache.hadoop.hdfsproxy.TestHdfsProxy FAILED Could somebody have a look on these failed test cases? Or tell me if I set anything wrong in my environment? Many thanks. PS: I referred to http://wiki.apache.org/hadoop/HadoopJavaVersions about setting the testing environment. -- Best Regards, Li Yu On 2 August 2011 19:22, Steve Loughran ste...@apache.org wrote: On 29/07/11 17:51, Suresh Srinivas wrote: I'd like to get HADOOP-7468 in, which deletes log4j.properties from the JAR. Someone did a patch for it yesterday I patched trunk but not the 20.20x branch This bug is not marked as a blocker. In that case I think we should pick this up in 205 release that is going to out soon.
Re: [VOTE] Release 0.20.204.0-rc0
On Aug 8, 2011, at 8:36 AM, Yu Li wrote: Hi all, I've just run unit test of 0.20.204 using SUN jdk1.6.0_21, on a 64bit RHEL machine, and find the following cases failed: [junit] Test org.apache.hadoop.mapred.TestJobTrackerRestart FAILED (timeout) I hit this one too. If you look at that test case, you'll see it has an @Ignore on it. For some unknown reason, when you use ant 1.8.2 junit does the wrong thing. Use ant 1.7.1 and the test cases will be properly ignored. -- Owen
Re: [VOTE] Release 0.20.204.0-rc0
Thanks Owen, for the quick and helpful response! By removing those test cases marked as @Ignored, there're still 3 failed test cases for 0.20.203: [junit] Test org.apache.hadoop.filecache.TestMRWithDistributedCache FAILED [junit] Test org.apache.hadoop.filecache.TestTrackerDistributedCacheManager FAILED [junit] Test org.apache.hadoop.hdfsproxy.TestHdfsProxy FAILED and 3 failed, 1 unstable cases for 0.20.204: [junit] Test org.apache.hadoop.filecache.TestMRWithDistributedCache FAILED [junit] Test org.apache.hadoop.filecache.TestTrackerDistributedCacheManager FAILED [junit] Test org.apache.hadoop.mapred.TestJobTrackerRestartWithCS FAILED (timeout) [junit] Test org.apache.hadoop.mapred.TestRackAwareTaskPlacement -- FAILED twice, SUCCEED twice Has anybody met with these case failures? Thanks. -- Best Regards, Li Yu On 9 August 2011 00:26, Owen O'Malley o...@hortonworks.com wrote: On Aug 8, 2011, at 8:36 AM, Yu Li wrote: Hi all, I've just run unit test of 0.20.204 using SUN jdk1.6.0_21, on a 64bit RHEL machine, and find the following cases failed: [junit] Test org.apache.hadoop.mapred.TestJobTrackerRestart FAILED (timeout) I hit this one too. If you look at that test case, you'll see it has an @Ignore on it. For some unknown reason, when you use ant 1.8.2 junit does the wrong thing. Use ant 1.7.1 and the test cases will be properly ignored. -- Owen
Re: [VOTE] Release 0.20.204.0-rc0
On Wed, Aug 3, 2011 at 2:14 PM, Matt Foley mfo...@hortonworks.com wrote: So, how are we doing with 0.20.204 content and trunk given the above proposal? Very well, in fact. Matt, Suresh and I have done a detailed analysis (separate email), please take a look. Here's the analysis of changes in 204 vs trunk. We believe that ALL the changes in 204 are either already in trunk or do not need to be in trunk. Here is the list of 204 items not already in trunk, and their categorization. Please, if anyone thinks we've missed something, bring it to my attention and if it isn't already in trunk we will get it into trunk as expeditiously as possible. Thanks, --Matt Looks good to me Matt. Thanks for doing the analysis. I think the regression wrt trunk are from the original cut of the branch and don't need to block the 204 release, ie the trunk first discussion is IMO an orthogonal thread. Thanks, Eli
Re: [VOTE] Release 0.20.204.0-rc0
Can we add
* HADOOP-6942 Ability for having user's classes take precedence over the
system classes for tasks' classpath
It's pretty bad in a sense that it's not on trunk but 0.20.204 and CDH3 both
have this *using different parameters*.
Koji
On 8/3/11 2:14 PM, Matt Foley mfo...@hortonworks.com wrote:
So, how are we doing with 0.20.204 content and trunk given the above
proposal? Very well, in fact. Matt, Suresh and I have done a detailed
analysis (separate email), please take a look.
Here's the analysis of changes in 204 vs trunk. We believe that ALL the
changes in 204 are either already in trunk or do not need to be in trunk.
Here is the list of 204 items not already in trunk, and their
categorization.
Please, if anyone thinks we've missed something, bring it to my attention
and if it isn't already in trunk we will get it into trunk as expeditiously
as possible.
Thanks,
--Matt
Not needed for trunk:
HDFS-1758. Make Web UI JSP pages thread safe. (Tanping via suresh) (Not a
problem in trunk)
HDFS-2057. Wait time to terminate the threads causes unit tests to take
longer time. (Bharath Mundlapudi via suresh) (Not a problem in trunk)
HDFS-1878. TestHDFSServerPorts unit test failure - race condition in
FSNamesystem.close() causes NullPointerException without serious
consequence. (mattf) (not a problem in trunk)
HDFS-1842. Handle editlog opcode conflict with 0.20.203 during upgrade, by
throwing an error to indicate the editlog needs to be empty. (suresh)
(Handled by HDFS-1824)
HDFS-2218. Disable TestHdfsProxy.testHdfsProxyInterface in automated test
suite for 0.20-security-204 release. (Matt Foley) (Not a problem in trunk)
HDFS-2044. TestQueueProcessingStatistics failing automatic test due to
timing issues. (mattf) (not a problem in trunk)
HADOOP-7459. Remove jdk-1.6.0 dependency check from rpm. (omalley) (replaced
by HDFS-2156)
HADOOP-7398. Suppress warnings about use of HADOOP_HOME. (omalley) (not a
problem in trunk)
HADOOP-7369. Fix permissions in tarball for sbin/* and libexec/* (omalley)
(not a problem in trunk)
HADOOP-7373. Fix {start,stop}-{dfs,mapred} and hadoop-daemons.sh from trying
to use the wrong bin directory. (omalley) (not a problem in trunk)
HADOOP-7475. Fix hadoop-setup-single-node.sh to reflect new layout. (eyang
via omalley) (not a problem in trunk)
Back port from trunk:
MAPREDUCE-2524. Port reduce failure reporting semantics from trunk, to fail
faulty maps more aggressively. (Thomas Graves via cdouglas)
MAPREDUCE-2479. Move distributed cache cleanup to a background task,
backporting MAPREDUCE-1568. (Robert Joseph Evans via cdouglas)
HDFS-2023. Backport of NPE for File.list and File.listFiles. Merged ports
of HADOOP-7322, HDFS-1934, HADOOP-7342, and HDFS-2019. (Bharath Mundlapudi
via mattf)
HADOOP-7248. Update eclipse target to generate .classpath from ivy config.
(Thomas Graves and Tom White via cdouglas) (from HADOOP-6407)
HADOOP-7274. Fix typos in IOUtils. (Jonathan Eagles via cdouglas) (from
HADOOP-7057)
HADOOP-7277. Add generation of run configurations to eclipse target.
(Jeffrey Naisbitt and Philip Zeyliger via cdouglas) (from HADOOP-5911)
HADOOP-7364. TestMiniMRDFSCaching fails if test.build.dir is set to
something other than build/test. (Thomas Graves via mahadev) (from
MAPREDUCE-2575)
Already in trunk for MRV2:
MAPREDUCE-2558. Add queue-level metrics 0.20-security branch (test fixes)
(Jeffrey Naisbitt via mahadev)
MAPREDUCE-2418. Show job errors in JobHistory page. (Siddharth Seth via
acmurthy) (Already in MR279)
MAPREDUCE-2411. Force an exception when the queue has an invalid name or its
ACLs are misconfigured. (Dick King via cdouglas) (Already in MR279)
Waiting for MR279 merge:
MAPREDUCE-2429. Validate JVM in TaskUmbilicalProtocol. (Siddharth Seth via
acmurthy)
MAPREDUCE-2447. Fix Child.java to set Task.jvmContext sooner to avoid corner
cases in error handling. (Siddharth Seth via acmurthy)
MapReduce v1 exceptions:
MAPREDUCE-2415. Distribute the user task logs on to multiple disks.
(Bharath Mundlapudi via omalley)
MAPREDUCE-2413. TaskTracker should handle disk failures by reinitializing
itself. (Ravi Gummadi and Jagane Sundar via omalley)
MAPREDUCE-2621. TestCapacityScheduler fails with Queue q1 does not
exist. (Sherry Chen via mahadev)
MAPREDUCE-2535. Fix NPE in JobClient caused by retirement. (Robert Joseph
Evans via cdouglas)
MAPREDUCE-2555. Avoid sprious logging from completedtasks. (Thomas Graves
via cdouglas)
MAPREDUCE-2443. Fix TaskAspect for TaskUmbilicalProtocol.ping(..).
(Siddharth Seth via szetszwo)
On Wed, Aug 3, 2011 at 2:02 PM, Arun C Murthy a...@hortonworks.com wrote:
On Aug 2, 2011, at 4:28 AM, Steve Loughran wrote:
I'm getting confused about release roadmaps right now
Is there somewhere that lists the (proposed) timetable for the 0.20.204,
0.20.205, 0.22, 0.23 releases?
Since I was among the people who started the 'security on
Re: [VOTE] Release 0.20.204.0-rc0
Hi, Four critical patches have been applied to 0.20-security-204, and release candidate 0.20.204-rc1 is now ready for evaluation. The signed release is available at http://people.apache.org/~mattf/hadoop-0.20.204-rc1/ A successful build and test under Jenkins may be examined at https://builds.apache.org/view/G-L/view/Hadoop/job/Hadoop-0.20.204-Build/24/ The four changes since rc0 are: r1152887 | mattf | 2011-08-01 11:32:12 -0700 (Mon, 01 Aug 2011) | 1 line HDFS-2218. Disable TestHdfsProxy.testHdfsProxyInterface in automated test suite for 0.20-security-204 release. r1152037 | gkesavan | 2011-07-28 23:39:42 + (Thu, 28 Jul 2011) | 1 line HADOOP-7356. Fix bin scripts to support dev build environment r1150862 | ddas | 2011-07-25 19:32:59 + (Mon, 25 Jul 2011) | 1 line Merge -r 1150859:1150860 from branch-0.20-security onto branch-0.20-security-204 r1150857 | ddas | 2011-07-25 19:28:14 + (Mon, 25 Jul 2011) | 1 line MAPREDUCE-2621. Merge -r 1150527:1150528 from branch-0.20-security onto branch-0.20-security-204 Although Owen is the RM for this release, he requested assistance in progressing the release while he is traveling. Please resume the 0.20.204 release vote today, using this rc1 candidate. Thank you, --Matt On Fri, Jul 29, 2011 at 9:51 AM, Suresh Srinivas sur...@hortonworks.comwrote: New release candidate will be out soon that fixes the Jenkins failures. Vote will resume on that RC. Regards, Suresh
Re: [VOTE] Release 0.20.204.0-rc0
On 02/08/11 11:00, Matt Foley wrote: Hi, Four critical patches have been applied to 0.20-security-204, and release candidate 0.20.204-rc1 is now ready for evaluation. The signed release is available at http://people.apache.org/~mattf/hadoop-0.20.204-rc1/ A successful build and test under Jenkins may be examined at https://builds.apache.org/view/G-L/view/Hadoop/job/Hadoop-0.20.204-Build/24/ I'm getting confused about release roadmaps right now Is there somewhere that lists the (proposed) timetable for the 0.20.204, 0.20.205, 0.22, 0.23 releases? It sounds like any non-critical problem in 20.204rc0 is intended to go into to the 0.20.205 release. Correct? If so is there a release manager or can I go ahead and patch in the normal RTC process?
Re: [VOTE] Release 0.20.204.0-rc0
On Aug 2, 2011, at 4:28 AM, Steve Loughran wrote: I'm getting confused about release roadmaps right now branch-20 is the new trunk, given that features keep popping up in it rather than bug fixes.
Re: [VOTE] Release 0.20.204.0-rc0
On Aug 2, 2011, at 12:23 PM, Eli Collins wrote: However it is disappointing to see some of the features being developed on branch-20-security, rather being developed first on trunk and then ported to branch-20-security. ... which was exactly my point.
Re: [VOTE] Release 0.20.204.0-rc0
On 29/07/11 03:13, Aaron T. Myers wrote: On Thu, Jul 28, 2011 at 7:08 PM, Arun C Murthya...@hortonworks.com wrote: But, it doesn't really matter... do folks feel strongly we should restart the vote on general? I don't think there's need to restart the vote. I only brought this up because I've heard from a few people that they didn't know a release vote was going on. Let's just send an email to general@ saying there's a vote going on on common-dev@, and from now on be sure to send votes to general@. As Eli already said, it doesn't matter which it is, as long as people know where to look. I'd like to rm the log4j.properties file; I'll apply the patch for this to the branch and build and test locally. Yes: test.
Re: [VOTE] Release 0.20.204.0-rc0
On 29/07/11 12:01, Steve Loughran wrote: On 29/07/11 03:13, Aaron T. Myers wrote: On Thu, Jul 28, 2011 at 7:08 PM, Arun C Murthya...@hortonworks.com wrote: But, it doesn't really matter... do folks feel strongly we should restart the vote on general? I don't think there's need to restart the vote. I only brought this up because I've heard from a few people that they didn't know a release vote was going on. Let's just send an email to general@ saying there's a vote going on on common-dev@, and from now on be sure to send votes to general@. As Eli already said, it doesn't matter which it is, as long as people know where to look. I'd like to rm the log4j.properties file; I'll apply the patch for this to the branch and build and test locally. Yes: test. I've committed the HADOOP-7468 patch to build.xml to stop conf/log4.properties going into the JAR to trunk. There's a separate patch for the 0.20.204 release, which I'd argue for inclusion 1. It doesn't impact the server code 2. It breaks any app downstream that wants its own log4j. To be precise, it causes inconsistent behaviour depending on the classpath ordering. This change isn't going to impact any of the hadoop scripts -including client side ones- that have a the conf/ dir on the classpath. -Steve
Re: [VOTE] Release 0.20.204.0-rc0
I can't believe we're holding a vote on a release that isn't passing the nightly build. If my vote was binding, I'd -1 it based upon that alone.
Re: [VOTE] Release 0.20.204.0-rc0
Allen, I think Giri already sent out an email for that. Below is the response from him. There'll be a new rc candidate soon. Hope that helps. thanks mahadev === This issue is fixed with Eric's patch for HADOOP-7356. Since Owen is out on vacation Iam working on getting the release tarball. -Giri On 7/28/11 1:56 PM, Giridharan Kesavan gkesa...@yahoo-inc.com wrote: Myself and Eric Yang are looking into this. -Giri On 7/28/11 12:04 PM, Allen Wittenauer awittena...@linkedin.com wrote: On Jul 25, 2011, at 7:05 PM, Owen O'Malley wrote: I've created a release candidate for 0.20.204.0 that I would like to release. It is available at: http://people.apache.org/~omalley/hadoop-0.20.204.0-rc0/ 0.20.204.0 has many fixes including disk fail in place and the new rpm and deb packages. Fail in place allows the DataNode and TaskTracker to continue after a hard drive fails. Is it still failing to build according to Jenkins? == On Fri, Jul 29, 2011 at 8:59 AM, Allen Wittenauer a...@apache.org wrote: I can't believe we're holding a vote on a release that isn't passing the nightly build. If my vote was binding, I'd -1 it based upon that alone.
Re: [VOTE] Release 0.20.204.0-rc0
I'd like to get HADOOP-7468 in, which deletes log4j.properties from the JAR. Someone did a patch for it yesterday This bug is not marked as a blocker. In that case I think we should pick this up in 205 release that is going to out soon. On Fri, Jul 29, 2011 at 4:04 AM, Steve Loughran ste...@apache.org wrote: Incidentally, has anyone tested on Java7. The Lucene team are unhappy: http://www.lucidimagination.**com/search/document/** 1a0d3986e48a9348/warning_**index_corruption_and_crashes_** in_apache_lucene_core_apache_**solr_with_java_7http://www.lucidimagination.com/search/document/1a0d3986e48a9348/warning_index_corruption_and_crashes_in_apache_lucene_core_apache_solr_with_java_7 I do not think this is blocker either. New release candidate will be out soon that fixes the Jenkins failures. Vote will resume on that RC. Regards, Suresh
Re: [VOTE] Release 0.20.204.0-rc0
On Jul 25, 2011, at 7:05 PM, Owen O'Malley wrote: I've created a release candidate for 0.20.204.0 that I would like to release. It is available at: http://people.apache.org/~omalley/hadoop-0.20.204.0-rc0/ 0.20.204.0 has many fixes including disk fail in place and the new rpm and deb packages. Fail in place allows the DataNode and TaskTracker to continue after a hard drive fails. Is it still failing to build according to Jenkins?
Re: [VOTE] Release 0.20.204.0-rc0
Myself and Eric Yang are looking into this. -Giri On 7/28/11 12:04 PM, Allen Wittenauer awittena...@linkedin.com wrote: On Jul 25, 2011, at 7:05 PM, Owen O'Malley wrote: I've created a release candidate for 0.20.204.0 that I would like to release. It is available at: http://people.apache.org/~omalley/hadoop-0.20.204.0-rc0/ 0.20.204.0 has many fixes including disk fail in place and the new rpm and deb packages. Fail in place allows the DataNode and TaskTracker to continue after a hard drive fails. Is it still failing to build according to Jenkins?
Re: [VOTE] Release 0.20.204.0-rc0
Nope. general@ is only for announcements. AFAIK Votes are developer activities. Arun On Jul 28, 2011, at 5:11 PM, Aaron T. Myers wrote: Shouldn't this vote be taking place on general@, instead of common-dev@? I'm under the impression that that is where all votes are supposed to take place. Please correct me if I am wrong about that. -- Aaron T. Myers Software Engineer, Cloudera On Thu, Jul 28, 2011 at 5:02 PM, Giridharan Kesavan gkesa...@yahoo-inc.comwrote: This issue is fixed with Eric's patch for HADOOP-7356. Since Owen is out on vacation Iam working on getting the release tarball. -Giri On 7/28/11 1:56 PM, Giridharan Kesavan gkesa...@yahoo-inc.com wrote: Myself and Eric Yang are looking into this. -Giri On 7/28/11 12:04 PM, Allen Wittenauer awittena...@linkedin.com wrote: On Jul 25, 2011, at 7:05 PM, Owen O'Malley wrote: I've created a release candidate for 0.20.204.0 that I would like to release. It is available at: http://people.apache.org/~omalley/hadoop-0.20.204.0-rc0/ 0.20.204.0 has many fixes including disk fail in place and the new rpm and deb packages. Fail in place allows the DataNode and TaskTracker to continue after a hard drive fails. Is it still failing to build according to Jenkins?
RE: [VOTE] Release 0.20.204.0-rc0
I saw @jeric14's tweet about 0.20.204 vote last night, and was about to reply, because I could not see any vote on the general@ mailing list. Yes, toy are right @atm, the vote should be on general@. - milind --- Milind Bhandarkar -Original Message- From: Aaron T. Myers [mailto:a...@cloudera.com] Sent: Thursday, July 28, 2011 5:12 PM To: common-dev@hadoop.apache.org Subject: Re: [VOTE] Release 0.20.204.0-rc0 Shouldn't this vote be taking place on general@, instead of common-dev@? I'm under the impression that that is where all votes are supposed to take place. Please correct me if I am wrong about that. -- Aaron T. Myers Software Engineer, Cloudera On Thu, Jul 28, 2011 at 5:02 PM, Giridharan Kesavan gkesa...@yahoo-inc.comwrote: This issue is fixed with Eric's patch for HADOOP-7356. Since Owen is out on vacation Iam working on getting the release tarball. -Giri On 7/28/11 1:56 PM, Giridharan Kesavan gkesa...@yahoo-inc.com wrote: Myself and Eric Yang are looking into this. -Giri On 7/28/11 12:04 PM, Allen Wittenauer awittena...@linkedin.com wrote: On Jul 25, 2011, at 7:05 PM, Owen O'Malley wrote: I've created a release candidate for 0.20.204.0 that I would like to release. It is available at: http://people.apache.org/~omalley/hadoop-0.20.204.0-rc0/ 0.20.204.0 has many fixes including disk fail in place and the new rpm and deb packages. Fail in place allows the DataNode and TaskTracker to continue after a hard drive fails. Is it still failing to build according to Jenkins?
RE: [VOTE] Release 0.20.204.0-rc0
Somehow I remember that the 0.20.203.0 vote was carried out on general@ Here is a message from the archive: http://mail-archives.apache.org/mod_mbox/hadoop-general/201105.mbox/browser - milind --- Milind Bhandarkar -Original Message- From: Arun C Murthy [mailto:a...@hortonworks.com] Sent: Thursday, July 28, 2011 5:27 PM To: common-dev@hadoop.apache.org Subject: Re: [VOTE] Release 0.20.204.0-rc0 Nope. general@ is only for announcements. AFAIK Votes are developer activities. Arun On Jul 28, 2011, at 5:11 PM, Aaron T. Myers wrote: Shouldn't this vote be taking place on general@, instead of common-dev@? I'm under the impression that that is where all votes are supposed to take place. Please correct me if I am wrong about that. -- Aaron T. Myers Software Engineer, Cloudera On Thu, Jul 28, 2011 at 5:02 PM, Giridharan Kesavan gkesa...@yahoo-inc.comwrote: This issue is fixed with Eric's patch for HADOOP-7356. Since Owen is out on vacation Iam working on getting the release tarball. -Giri On 7/28/11 1:56 PM, Giridharan Kesavan gkesa...@yahoo-inc.com wrote: Myself and Eric Yang are looking into this. -Giri On 7/28/11 12:04 PM, Allen Wittenauer awittena...@linkedin.com wrote: On Jul 25, 2011, at 7:05 PM, Owen O'Malley wrote: I've created a release candidate for 0.20.204.0 that I would like to release. It is available at: http://people.apache.org/~omalley/hadoop-0.20.204.0-rc0/ 0.20.204.0 has many fixes including disk fail in place and the new rpm and deb packages. Fail in place allows the DataNode and TaskTracker to continue after a hard drive fails. Is it still failing to build according to Jenkins?
Re: [VOTE] Release 0.20.204.0-rc0
In the past we've carried it out on common-dev: http://hadoop-common.472056.n3.nabble.com/VOTE-Release-Hadoop-0-21-0-candidate-2-td1181981.html Arun On Jul 28, 2011, at 5:33 PM, milind.bhandar...@emc.com wrote: Somehow I remember that the 0.20.203.0 vote was carried out on general@ Here is a message from the archive: http://mail-archives.apache.org/mod_mbox/hadoop-general/201105.mbox/browser - milind --- Milind Bhandarkar -Original Message- From: Arun C Murthy [mailto:a...@hortonworks.com] Sent: Thursday, July 28, 2011 5:27 PM To: common-dev@hadoop.apache.org Subject: Re: [VOTE] Release 0.20.204.0-rc0 Nope. general@ is only for announcements. AFAIK Votes are developer activities. Arun On Jul 28, 2011, at 5:11 PM, Aaron T. Myers wrote: Shouldn't this vote be taking place on general@, instead of common-dev@? I'm under the impression that that is where all votes are supposed to take place. Please correct me if I am wrong about that. -- Aaron T. Myers Software Engineer, Cloudera On Thu, Jul 28, 2011 at 5:02 PM, Giridharan Kesavan gkesa...@yahoo-inc.comwrote: This issue is fixed with Eric's patch for HADOOP-7356. Since Owen is out on vacation Iam working on getting the release tarball. -Giri On 7/28/11 1:56 PM, Giridharan Kesavan gkesa...@yahoo-inc.com wrote: Myself and Eric Yang are looking into this. -Giri On 7/28/11 12:04 PM, Allen Wittenauer awittena...@linkedin.com wrote: On Jul 25, 2011, at 7:05 PM, Owen O'Malley wrote: I've created a release candidate for 0.20.204.0 that I would like to release. It is available at: http://people.apache.org/~omalley/hadoop-0.20.204.0-rc0/ 0.20.204.0 has many fixes including disk fail in place and the new rpm and deb packages. Fail in place allows the DataNode and TaskTracker to continue after a hard drive fails. Is it still failing to build according to Jenkins?
Re: [VOTE] Release 0.20.204.0-rc0
We've done both, even within a branch (0.20.0 was voted on core-dev@ and 0.20.2 on general@). The bylaws suggest general@ should be used, which seems to make sense since we're releasing common, hdfs and mr. I think either works as long as people know where to check. http://hadoop.apache.org/bylaws.html Voting Decisions regarding the project are made by votes on the primary project development mailing list (gene...@hadoop.apache.org) On Thu, Jul 28, 2011 at 5:40 PM, Arun C Murthy a...@hortonworks.com wrote: In the past we've carried it out on common-dev: http://hadoop-common.472056.n3.nabble.com/VOTE-Release-Hadoop-0-21-0-candidate-2-td1181981.html Arun On Jul 28, 2011, at 5:33 PM, milind.bhandar...@emc.com wrote: Somehow I remember that the 0.20.203.0 vote was carried out on general@ Here is a message from the archive: http://mail-archives.apache.org/mod_mbox/hadoop-general/201105.mbox/browser - milind --- Milind Bhandarkar -Original Message- From: Arun C Murthy [mailto:a...@hortonworks.com] Sent: Thursday, July 28, 2011 5:27 PM To: common-dev@hadoop.apache.org Subject: Re: [VOTE] Release 0.20.204.0-rc0 Nope. general@ is only for announcements. AFAIK Votes are developer activities. Arun On Jul 28, 2011, at 5:11 PM, Aaron T. Myers wrote: Shouldn't this vote be taking place on general@, instead of common-dev@? I'm under the impression that that is where all votes are supposed to take place. Please correct me if I am wrong about that. -- Aaron T. Myers Software Engineer, Cloudera On Thu, Jul 28, 2011 at 5:02 PM, Giridharan Kesavan gkesa...@yahoo-inc.comwrote: This issue is fixed with Eric's patch for HADOOP-7356. Since Owen is out on vacation Iam working on getting the release tarball. -Giri On 7/28/11 1:56 PM, Giridharan Kesavan gkesa...@yahoo-inc.com wrote: Myself and Eric Yang are looking into this. -Giri On 7/28/11 12:04 PM, Allen Wittenauer awittena...@linkedin.com wrote: On Jul 25, 2011, at 7:05 PM, Owen O'Malley wrote: I've created a release candidate for 0.20.204.0 that I would like to release. It is available at: http://people.apache.org/~omalley/hadoop-0.20.204.0-rc0/ 0.20.204.0 has many fixes including disk fail in place and the new rpm and deb packages. Fail in place allows the DataNode and TaskTracker to continue after a hard drive fails. Is it still failing to build according to Jenkins?
Re: [VOTE] Release 0.20.204.0-rc0
Done. Thanks. On Jul 28, 2011, at 7:13 PM, Aaron T. Myers wrote: On Thu, Jul 28, 2011 at 7:08 PM, Arun C Murthy a...@hortonworks.com wrote: But, it doesn't really matter... do folks feel strongly we should restart the vote on general? I don't think there's need to restart the vote. I only brought this up because I've heard from a few people that they didn't know a release vote was going on. Let's just send an email to general@ saying there's a vote going on on common-dev@, and from now on be sure to send votes to general@. As Eli already said, it doesn't matter which it is, as long as people know where to look. -- Aaron T. Myers Software Engineer, Cloudera
