Re: [VOTE] Release Apache Hadoop 2.0.6-alpha (RC1)
+1 Downloaded source tarball Verified MD5 Verified Signature Run apache-rat:check Did a dist build Started pseudo cluster Run a couple of MR examples Tested HttpFS On Thu, Aug 15, 2013 at 10:29 PM, Konstantin Boudnik wrote: > All, > > I have created a release candidate (rc1) for hadoop-2.0.6-alpha that I > would > like to release. > > This is a stabilization release that includes fixed for a couple a of > issues > as outlined on the security list. > > The RC is available at: > http://people.apache.org/~cos/hadoop-2.0.6-alpha-rc1/ > The RC tag in svn is here: > http://svn.apache.org/repos/asf/hadoop/common/tags/release-2.0.6-alpha-rc1 > > The maven artifacts are available via repository.apache.org. > > The only difference between rc0 and rc1 is ASL added to releasenotes.html > and > updated release dates in CHANGES.txt files. > > Please try the release bits and vote; the vote will run for the usual 7 > days. > > Thanks for your voting > Cos > > -- Alejandro
Re: [VOTE] Release Apache Hadoop 2.1.0-beta
I've been OOO (got a call to fix this bug), but just to clarify: We're ok with HA _not working at all_ with security enabled in 2.1.0-beta? That's the ramification of omitting HADOOP-9880. Daryn On Aug 16, 2013, at 9:20 PM, Arun C Murthy wrote: > Yep, there are quite a number of such fixes in 2.1.1 ATM, I think it will > serve us better to get 2.1.0 out and then quickly turn around to make 2.1.1. > > My current plan is to start work on 2.1.1 right after this release gets > complete… hopefully next week. > > thanks, > Arun > > On Aug 16, 2013, at 4:36 PM, Vinod Kumar Vavilapalli > wrote: > >> >> There are other such isolated and well understood bug-fixes that we pushed >> to 2.1.1 in the interesting of making progress with 2.1.0 and the >> corresponding API changes. >> >> 2.1.1 should happen soon enough after this. >> >> Thanks, >> +Vinod >> >> On Aug 16, 2013, at 4:22 PM, Roman Shaposhnik wrote: >> >>> What are the downsides of getting this fix into the 2.1? It appears >>> that the fix is pretty isolated and well understood. >>> >>> Thoughts? >>> >>> Thanks, >>> Roman. >>> >>> On Fri, Aug 16, 2013 at 3:04 PM, Kihwal Lee wrote: I've changed the target version of HADOOP-9880 to 2.1.1. Please change it back, if you feel that it needs to be in 2.1.0-beta. Kihwal From: Kihwal Lee To: Arun Murthy ; "common-dev@hadoop.apache.org" Cc: "mapreduce-...@hadoop.apache.org" ; "hdfs-...@hadoop.apache.org" ; "yarn-...@hadoop.apache.org" Sent: Friday, August 16, 2013 4:55 PM Subject: Re: [VOTE] Release Apache Hadoop 2.1.0-beta It's your call, Arun. I.e. as long you believe rc2 meets the expectations and objectives of 2.1.0-beta. Kihwal From: Arun Murthy To: "common-dev@hadoop.apache.org" Cc: Kihwal Lee ; "mapreduce-...@hadoop.apache.org" ; "hdfs-...@hadoop.apache.org" ; "yarn-...@hadoop.apache.org" Sent: Friday, August 16, 2013 3:44 PM Subject: Re: [VOTE] Release Apache Hadoop 2.1.0-beta That makes sense too. On Aug 16, 2013, at 10:39 AM, Vinod Kumar Vavilapalli wrote: > > We need to make a call on what blockers will be. From my limited > understanding, this doesn't seem like a API or a compatibility issue. Can > we not fix it in subsequent bug-fix releases? > > I do see a lot of follow up releases to 2.1.0. Getting this release out > will help downstream projects start testing with all the API stuff that > has already gone in 2.1.0. > > Thanks, > +Vinod > > On Aug 16, 2013, at 10:13 AM, Kihwal Lee wrote: > >> We have found HADOOP-9880, which prevents Namenode HA from running with >> security. >> >> Kihwal >> >> >> >> From: Arun C Murthy >> To: "common-dev@hadoop.apache.org" ; >> "hdfs-...@hadoop.apache.org" ; >> "mapreduce-...@hadoop.apache.org" ; >> "yarn-...@hadoop.apache.org" >> Sent: Thursday, August 15, 2013 4:15 PM >> Subject: [VOTE] Release Apache Hadoop 2.1.0-beta >> >> >> Folks, >> >> I've created a release candidate (rc2) for hadoop-2.1.0-beta that I >> would like to get released - this fixes the bugs we saw since the last >> go-around (rc1). >> >> The RC is available at: >> http://people.apache.org/~acmurthy/hadoop-2.1.0-beta-rc2/ >> The RC tag in svn is here: >> http://svn.apache.org/repos/asf/hadoop/common/tags/release-2.1.0-beta-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/ >> >> >> >> -- >> 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. > > > -- > 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 appli
[jira] [Resolved] (HADOOP-9882) Trunk doesn't compile
[ https://issues.apache.org/jira/browse/HADOOP-9882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kihwal Lee resolved HADOOP-9882. Resolution: Not A Problem > Trunk doesn't compile > - > > Key: HADOOP-9882 > URL: https://issues.apache.org/jira/browse/HADOOP-9882 > Project: Hadoop Common > Issue Type: Bug > Components: build >Reporter: Jean-Baptiste Onofré > > Currently, trunk does not compile (in hadoop-common-project/hadoop-common > module): > [ERROR] Failed to execute goal > org.apache.hadoop:hadoop-maven-plugins:3.0.0-SNAPSHOT:protoc (compile-protoc) > on project hadoop-common: org.apache.maven.plugin.MojoExecutionException: > protoc version is 'libprotoc 2.4.1', expected version is '2.5.0' -> [Help 1] > I gonna fix that. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HADOOP-9883) Local mode FileNotFoundException: File does not exist
Abin Shahab created HADOOP-9883: --- Summary: Local mode FileNotFoundException: File does not exist Key: HADOOP-9883 URL: https://issues.apache.org/jira/browse/HADOOP-9883 Project: Hadoop Common Issue Type: Bug Affects Versions: 2.0.2-alpha Environment: Centos 6.3 Hadoop 2.0.2-alpha Hive 0.10.0 Reporter: Abin Shahab Priority: Critical Hive jobs in local mode fail with the error posted below. The jar file that's not being found exists and has the following access: > ls -l hive-0.10.0/lib/hive-builtins-0.10.0.jar rw-rw-r-- 1 ashahab ashahab 3914 Dec 18 2012 hive-0.10.0/lib/hive-builtins-0.10.0.jar Steps to reproduce [vcc_chaiken@HadoopDesktop0 ~]$ hive Logging initialized using configuration in jar:file:/opt/hive/lib/hive-common-0.10.0.jar!/hive-log4j.properties Hive history file=/disk1/hive/log/vcc_chaiken/hive_job_log_vcc_chaiken_201307162119_876702406.txt hive> create database chaiken_test_00; OK Time taken: 1.675 seconds hive> use chaiken_test_00; OK Time taken: 0.029 seconds hive> create table chaiken_test_table(foo INT); OK Time taken: 0.301 seconds hive> select count(*) from chaiken_test_table; Total MapReduce jobs = 1 Launching Job 1 out of 1 Number of reduce tasks determined at compile time: 1 In order to change the average load for a reducer (in bytes): set hive.exec.reducers.bytes.per.reducer= In order to limit the maximum number of reducers: set hive.exec.reducers.max= In order to set a constant number of reducers: set mapred.reduce.tasks= Starting Job = job_1373902166027_0061, Tracking URL = http://100-01-09.sc1.verticloud.com:8088/proxy/application_1373902166027_0061/ Kill Command = /opt/hadoop/bin/hadoop job -kill job_1373902166027_0061 Hadoop job information for Stage-1: number of mappers: 1; number of reducers: 1 2013-07-16 21:20:25,617 Stage-1 map = 0%, reduce = 0% 2013-07-16 21:20:30,026 Stage-1 map = 100%, reduce = 0%, Cumulative CPU 1.13 sec 2013-07-16 21:20:31,110 Stage-1 map = 100%, reduce = 0%, Cumulative CPU 1.13 sec 2013-07-16 21:20:32,188 Stage-1 map = 100%, reduce = 0%, Cumulative CPU 1.13 sec 2013-07-16 21:20:33,270 Stage-1 map = 100%, reduce = 0%, Cumulative CPU 1.13 sec 2013-07-16 21:20:34,356 Stage-1 map = 100%, reduce = 0%, Cumulative CPU 1.13 sec 2013-07-16 21:20:35,455 Stage-1 map = 100%, reduce = 100%, Cumulative CPU 3.4 sec MapReduce Total cumulative CPU time: 3 seconds 400 msec Ended Job = job_1373902166027_0061 MapReduce Jobs Launched: Job 0: Map: 1 Reduce: 1 Cumulative CPU: 3.4 sec HDFS Read: 246 HDFS Write: 2 SUCCESS Total MapReduce CPU Time Spent: 3 seconds 400 msec OK 0 Time taken: 20.627 seconds hive> set hive.exec.mode.local.auto; hive.exec.mode.local.auto=false hive> set hive.exec.mode.local.auto=true; hive> set hive.exec.mode.local.auto; hive.exec.mode.local.auto=true hive> select count(*) from chaiken_test_table; Automatically selecting local only mode for query Total MapReduce jobs = 1 Launching Job 1 out of 1 Number of reduce tasks determined at compile time: 1 In order to change the average load for a reducer (in bytes): set hive.exec.reducers.bytes.per.reducer= In order to limit the maximum number of reducers: set hive.exec.reducers.max= In order to set a constant number of reducers: set mapred.reduce.tasks= 13/07/16 21:20:49 WARN conf.Configuration: file:/disk1/hive/scratch/vcc_chaiken/hive_2013-07-16_21-20-47_210_4351529322776236119/-local-10002/jobconf.xml:an attempt to override final parameter: mapreduce.job.end-notification.max.retry.interval; Ignoring. 13/07/16 21:20:49 WARN conf.Configuration: file:/disk1/hive/scratch/vcc_chaiken/hive_2013-07-16_21-20-47_210_4351529322776236119/-local-10002/jobconf.xml:an attempt to override final parameter: mapreduce.job.end-notification.max.attempts; Ignoring. WARNING: org.apache.hadoop.metrics.jvm.EventCounter is deprecated. Please use org.apache.hadoop.log.metrics.EventCounter in all the log4j.properties files. Execution log at: /tmp/vcc_chaiken/vcc_chaiken_20130716212020_4db219e0-cf40-4e73-ac0d-a1d2eaca934e.log java.io.FileNotFoundException: File does not exist: /opt/hive/lib/hive-builtins-0.10.0.jar at org.apache.hadoop.hdfs.DistributedFileSystem.getFileStatus(DistributedFileSystem.java:782) at org.apache.hadoop.mapreduce.filecache.ClientDistributedCacheManager.getFileStatus(ClientDistributedCacheManager.java:208) at org.apache.hadoop.mapreduce.filecache.ClientDistributedCacheManager.determineTimestamps(ClientDistributedCacheManager.java:71) at org.apache.hadoop.mapreduce.JobSubmitter.copyAndConfigureFiles(JobSubmitter.java:252) at org.apache.hadoop.mapreduce.JobSubmitter.copyAndConfigureFiles(JobSubmitter.java:290) at org.apache.hadoop.mapreduce.JobSubmitter.submitJobInternal(JobSubmitter.java:361) at org.apache.hadoop.mapreduce.Job$11.run(Job.java:1218) at org.apache.hadoop.mapreduce.Job$11.run(Job.java:1215)
[jira] [Created] (HADOOP-9884) Hadoop calling du -sk can cause huge load
Alex Newman created HADOOP-9884: --- Summary: Hadoop calling du -sk can cause huge load Key: HADOOP-9884 URL: https://issues.apache.org/jira/browse/HADOOP-9884 Project: Hadoop Common Issue Type: Bug Reporter: Alex Newman On numerous occasions we've had customers worry about slowness while hadoop calls du -sk underneath the hood. For most of these users getting the information from df would be sufficient and much faster. In fact there is a hack going around, that is quiet common that replaces df with du. Sometimes people have to tune the vcache. What if we just allowed users to use the df information instead of the du information with a patch and config setting. I'd be glad to code it up -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HADOOP-9885) Chocolatey package for Windows users
Andrew Pennebaker created HADOOP-9885: - Summary: Chocolatey package for Windows users Key: HADOOP-9885 URL: https://issues.apache.org/jira/browse/HADOOP-9885 Project: Hadoop Common Issue Type: Improvement Components: build Environment: Chocolatey (http://chocolatey.org/) Windows XP+ Reporter: Andrew Pennebaker Priority: Minor Installing Hadoop is beyond some Windows users. Could we please offer a Chocolatey package to make this easier? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HADOOP-9886) Turn warning message in RetryInvocationHandler to a debub
Arpit Gupta created HADOOP-9886: --- Summary: Turn warning message in RetryInvocationHandler to a debub Key: HADOOP-9886 URL: https://issues.apache.org/jira/browse/HADOOP-9886 Project: Hadoop Common Issue Type: Bug Affects Versions: 2.1.0-beta Reporter: Arpit Gupta Assignee: Arpit Gupta Priority: Minor Fix For: 2.1.1-beta Currently if debug is not enabled we display a warning message when the client fails over to another namenode. This will happen for every call that goes to the failed over namenode. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: [VOTE] Release Apache Hadoop 2.1.0-beta
Thanks for the clarification Daryn. That is what I was asking before when I said "From my limited understanding, this doesn't seem like a API or a compatibility issue. Can we not fix it in subsequent bug-fix releases? " Now, I was wavering as to whether we can omit this or not. There are other such things like YARN-1082 (RM restart doesn't work in security), YARN-49 (dist-shell in secure mode) etc. that is essentially a loss of some functionality in some cases (secure mode). Flipping back the question, aren't we okay release now with all the API changes that are already in and then immediately follow up with a bunch of bug-fix releases or wait till 'everything' gets fixed. Posing the question like that, I am willing to move ahead without waiting for these fixes, but that's just me. What do others think? Thanks, +Vinod On Aug 19, 2013, at 8:25 AM, Daryn Sharp wrote: > I've been OOO (got a call to fix this bug), but just to clarify: > > We're ok with HA _not working at all_ with security enabled in 2.1.0-beta? > That's the ramification of omitting HADOOP-9880. > > Daryn > > On Aug 16, 2013, at 9:20 PM, Arun C Murthy wrote: > >> Yep, there are quite a number of such fixes in 2.1.1 ATM, I think it will >> serve us better to get 2.1.0 out and then quickly turn around to make 2.1.1. >> >> My current plan is to start work on 2.1.1 right after this release gets >> complete… hopefully next week. >> >> thanks, >> Arun >> >> On Aug 16, 2013, at 4:36 PM, Vinod Kumar Vavilapalli >> wrote: >> >>> >>> There are other such isolated and well understood bug-fixes that we pushed >>> to 2.1.1 in the interesting of making progress with 2.1.0 and the >>> corresponding API changes. >>> >>> 2.1.1 should happen soon enough after this. >>> >>> Thanks, >>> +Vinod >>> >>> On Aug 16, 2013, at 4:22 PM, Roman Shaposhnik wrote: >>> What are the downsides of getting this fix into the 2.1? It appears that the fix is pretty isolated and well understood. Thoughts? Thanks, Roman. On Fri, Aug 16, 2013 at 3:04 PM, Kihwal Lee wrote: > I've changed the target version of HADOOP-9880 to 2.1.1. Please change > it back, if you feel that it needs to be in 2.1.0-beta. > > > Kihwal > > > > From: Kihwal Lee > To: Arun Murthy ; "common-dev@hadoop.apache.org" > > Cc: "mapreduce-...@hadoop.apache.org" ; > "hdfs-...@hadoop.apache.org" ; > "yarn-...@hadoop.apache.org" > Sent: Friday, August 16, 2013 4:55 PM > Subject: Re: [VOTE] Release Apache Hadoop 2.1.0-beta > > > It's your call, Arun. I.e. as long you believe rc2 meets the > expectations and objectives of 2.1.0-beta. > > Kihwal > > > > From: Arun Murthy > To: "common-dev@hadoop.apache.org" > Cc: Kihwal Lee ; "mapreduce-...@hadoop.apache.org" > ; "hdfs-...@hadoop.apache.org" > ; "yarn-...@hadoop.apache.org" > > Sent: Friday, August 16, 2013 3:44 PM > Subject: Re: [VOTE] Release Apache Hadoop 2.1.0-beta > > > That makes sense too. > > > On Aug 16, 2013, at 10:39 AM, Vinod Kumar Vavilapalli > wrote: > >> >> We need to make a call on what blockers will be. From my limited >> understanding, this doesn't seem like a API or a compatibility issue. >> Can we not fix it in subsequent bug-fix releases? >> >> I do see a lot of follow up releases to 2.1.0. Getting this release out >> will help downstream projects start testing with all the API stuff that >> has already gone in 2.1.0. >> >> Thanks, >> +Vinod >> >> On Aug 16, 2013, at 10:13 AM, Kihwal Lee wrote: >> >>> We have found HADOOP-9880, which prevents Namenode HA from running with >>> security. >>> >>> Kihwal >>> >>> >>> >>> From: Arun C Murthy >>> To: "common-dev@hadoop.apache.org" ; >>> "hdfs-...@hadoop.apache.org" ; >>> "mapreduce-...@hadoop.apache.org" ; >>> "yarn-...@hadoop.apache.org" >>> Sent: Thursday, August 15, 2013 4:15 PM >>> Subject: [VOTE] Release Apache Hadoop 2.1.0-beta >>> >>> >>> Folks, >>> >>> I've created a release candidate (rc2) for hadoop-2.1.0-beta that I >>> would like to get released - this fixes the bugs we saw since the last >>> go-around (rc1). >>> >>> The RC is available at: >>> http://people.apache.org/~acmurthy/hadoop-2.1.0-beta-rc2/ >>> The RC tag in svn is here: >>> http://svn.apache.org/repos/asf/hadoop/common/tags/release-2.1.0-beta-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
Re: [VOTE] Release Apache Hadoop 2.1.0-beta
Vinod, your thinking makes sense to me. My two cents are that we should hold off on fixes until 2.1.1-beta. Unless there are downstream projects that need it to work for integration testing. -Sandy On Mon, Aug 19, 2013 at 2:49 PM, Vinod Kumar Vavilapalli wrote: > > Thanks for the clarification Daryn. That is what I was asking before when > I said "From my limited understanding, this doesn't seem like a API or a > compatibility issue. Can we not fix it in subsequent bug-fix releases? " > > Now, I was wavering as to whether we can omit this or not. There are other > such things like YARN-1082 (RM restart doesn't work in security), YARN-49 > (dist-shell in secure mode) etc. that is essentially a loss of some > functionality in some cases (secure mode). > > Flipping back the question, aren't we okay release now with all the API > changes that are already in and then immediately follow up with a bunch of > bug-fix releases or wait till 'everything' gets fixed. > > Posing the question like that, I am willing to move ahead without waiting > for these fixes, but that's just me. > > What do others think? > > Thanks, > +Vinod > > On Aug 19, 2013, at 8:25 AM, Daryn Sharp wrote: > > I've been OOO (got a call to fix this bug), but just to clarify: > > We're ok with HA _not working at all_ with security enabled in 2.1.0-beta? > That's the ramification of omitting HADOOP-9880. > > Daryn > > On Aug 16, 2013, at 9:20 PM, Arun C Murthy wrote: > > Yep, there are quite a number of such fixes in 2.1.1 ATM, I think it will > serve us better to get 2.1.0 out and then quickly turn around to make 2.1.1. > > > My current plan is to start work on 2.1.1 right after this release gets > complete… hopefully next week. > > > thanks, > > Arun > > > On Aug 16, 2013, at 4:36 PM, Vinod Kumar Vavilapalli < > vino...@hortonworks.com> wrote: > > > > There are other such isolated and well understood bug-fixes that we pushed > to 2.1.1 in the interesting of making progress with 2.1.0 and the > corresponding API changes. > > > 2.1.1 should happen soon enough after this. > > > Thanks, > > +Vinod > > > On Aug 16, 2013, at 4:22 PM, Roman Shaposhnik wrote: > > > What are the downsides of getting this fix into the 2.1? It appears > > that the fix is pretty isolated and well understood. > > > Thoughts? > > > Thanks, > > Roman. > > > On Fri, Aug 16, 2013 at 3:04 PM, Kihwal Lee wrote: > > I've changed the target version of HADOOP-9880 to 2.1.1. Please change it > back, if you feel that it needs to be in 2.1.0-beta. > > > > Kihwal > > > > > > From: Kihwal Lee > > To: Arun Murthy ; "common-dev@hadoop.apache.org" < > common-dev@hadoop.apache.org> > > Cc: "mapreduce-...@hadoop.apache.org" ; " > hdfs-...@hadoop.apache.org" ; " > yarn-...@hadoop.apache.org" > > Sent: Friday, August 16, 2013 4:55 PM > > Subject: Re: [VOTE] Release Apache Hadoop 2.1.0-beta > > > > It's your call, Arun. I.e. as long you believe rc2 meets the expectations > and objectives of 2.1.0-beta. > > > Kihwal > > > > > > From: Arun Murthy > > To: "common-dev@hadoop.apache.org" > > Cc: Kihwal Lee ; "mapreduce-...@hadoop.apache.org" < > mapreduce-...@hadoop.apache.org>; "hdfs-...@hadoop.apache.org" < > hdfs-...@hadoop.apache.org>; "yarn-...@hadoop.apache.org" < > yarn-...@hadoop.apache.org> > > Sent: Friday, August 16, 2013 3:44 PM > > Subject: Re: [VOTE] Release Apache Hadoop 2.1.0-beta > > > > That makes sense too. > > > > On Aug 16, 2013, at 10:39 AM, Vinod Kumar Vavilapalli > > wrote: > > > > We need to make a call on what blockers will be. From my limited > understanding, this doesn't seem like a API or a compatibility issue. Can > we not fix it in subsequent bug-fix releases? > > > I do see a lot of follow up releases to 2.1.0. Getting this release out > will help downstream projects start testing with all the API stuff that has > already gone in 2.1.0. > > > Thanks, > > +Vinod > > > On Aug 16, 2013, at 10:13 AM, Kihwal Lee wrote: > > > We have found HADOOP-9880, which prevents Namenode HA from running with > security. > > > Kihwal > > > > > > From: Arun C Murthy > > To: "common-dev@hadoop.apache.org" ; " > hdfs-...@hadoop.apache.org" ; " > mapreduce-...@hadoop.apache.org" ; " > yarn-...@hadoop.apache.org" > > Sent: Thursday, August 15, 2013 4:15 PM > > Subject: [VOTE] Release Apache Hadoop 2.1.0-beta > > > > Folks, > > > I've created a release candidate (rc2) for hadoop-2.1.0-beta that I would > like to get released - this fixes the bugs we saw since the last go-around > (rc1). > > > The RC is available at: > http://people.apache.org/~acmurthy/hadoop-2.1.0-beta-rc2/ > > The RC tag in svn is here: > http://svn.apache.org/repos/asf/hadoop/common/tags/release-2.1.0-beta-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 > > Hort
Re: [VOTE] Release Apache Hadoop 2.1.0-beta
On Mon, Aug 19, 2013 at 2:49 PM, Vinod Kumar Vavilapalli wrote: > > Thanks for the clarification Daryn. That is what I was asking before when I > said "From my limited understanding, this doesn't seem like a API or a > compatibility issue. Can we not fix it in subsequent bug-fix releases? " > > Now, I was wavering as to whether we can omit this or not. There are other > such things like YARN-1082 (RM restart doesn't work in security), YARN-49 > (dist-shell in secure mode) etc. that is essentially a loss of some > functionality in some cases (secure mode). > > Flipping back the question, aren't we okay release now with all the API > changes that are already in and then immediately follow up with a bunch of > bug-fix releases or wait till 'everything' gets fixed. > > Posing the question like that, I am willing to move ahead without waiting > for these fixes, but that's just me. > > What do others think? Pushing a 2.1.0 out this week and following up with 2.1.1 in Sep might actually be a pretty good plan. That said, we have to be *really* conservative on what goes into 2.1.1 and make sure we can have it out on time. Thanks, Roman.
[jira] [Created] (HADOOP-9887) globStatus does not correctly handle paths starting with a drive spec on Windows
Chris Nauroth created HADOOP-9887:
-
Summary: globStatus does not correctly handle paths starting with
a drive spec on Windows
Key: HADOOP-9887
URL: https://issues.apache.org/jira/browse/HADOOP-9887
Project: Hadoop Common
Issue Type: Bug
Components: fs
Affects Versions: 3.0.0, 2.3.0
Reporter: Chris Nauroth
Recent file system changes have caused globStatus to stop working for paths
starting with a drive spec on Windows. The problem is most easily visible by
running {{TestFileUtil#createJarWithClassPath}} on Windows. This method
attempts a globStatus with pattern {{*\{.jar,.JAR\}}}, and it no longer
correctly identifies files at the path ending in .jar or .JAR.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
