[jira] [Resolved] (HADOOP-13170) TestOptionsParser in o.a.h.tools fails

[ https://issues.apache.org/jira/browse/HADOOP-13170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajesh Balamohan resolved HADOOP-13170. --- Resolution: Resolved Already got committed in HDFS-10397 yesterday in branch-2 and b

Re: Different JIRA permissions for HADOOP and HDFS

Added Arun Suresh into committer role in MAPREDUCE. Added Yufei Gu into contributor role in HDFS. Thanks, Akira On 5/18/16 14:08, Yufei Gu wrote: I guess I lost my contributor role in HDFS, since I cannot comment in HDFS. Best, Yufei On Tue, May 17, 2016 at 9:48 PM, Akira AJISAKA mailto:ajis

Re: Different JIRA permissions for HADOOP and HDFS

Hello Akira It looks like I can't Assign MAPREDUCE jiras to myself, so I guess my id (asuresh) has been removed from the committers/contributers role in MAPREDUCE (YARN, HADOOP and HDFS seem to be fine..) Cheers -Arun On Tue, May 17, 2016 at 9:48 PM, Akira AJISAKA wrote: > In HADOOP/HDFS/MAPRE

Re: Different JIRA permissions for HADOOP and HDFS

In HADOOP/HDFS/MAPREDUCE/YARN, I removed the administrators from contributor group. After that, added Varun into contributor roles. # Ray is already added into contributor roles. Hi contributors/committers, please tell me if you have lost your roles by mistake. > just remove a big chunk of th

Re: [DISCUSS] upgrade tomcat from 6.0.44 to 6.0.45 and use non apache.org mirror

> On May 17, 2016, at 8:32 PM, Wangda Tan wrote: > > I'm not sure if archive.apache.org enforces some new bandwidth limit > policies recently, I haven't seen such bandwidth limits before. We should > consider to fix it If more people complaint about such failures. Chances are, either:

Re: [DISCUSS] upgrade tomcat from 6.0.44 to 6.0.45 and use non apache.org mirror

I'm not sure if archive.apache.org enforces some new bandwidth limit policies recently, I haven't seen such bandwidth limits before. We should consider to fix it If more people complaint about such failures. A workaround for this issue is pass -Dtomcat.download.url to manual set a download url of

[jira] [Created] (HADOOP-13170) TestOptionsParser in o.a.h.tools fails

Rajesh Balamohan created HADOOP-13170: - Summary: TestOptionsParser in o.a.h.tools fails Key: HADOOP-13170 URL: https://issues.apache.org/jira/browse/HADOOP-13170 Project: Hadoop Common Is

[jira] [Created] (HADOOP-13169) Randomize file list in SimpleCopyListing

Rajesh Balamohan created HADOOP-13169: - Summary: Randomize file list in SimpleCopyListing Key: HADOOP-13169 URL: https://issues.apache.org/jira/browse/HADOOP-13169 Project: Hadoop Common

Is Hadoop's TooRunner thread-safe?

Hi experts I'm running into similar issues like http://stackoverflow.com/questions/22462665/is-hadoops-toorunner-thread-safe, the author's observation seem to make sense to me. However when I checked the hadoop github trunk I found the issue still not fixed. Is there any JIRA tracking this issue?

Re: Help with committing document to home.apache.org

Hi Lei, We don't need to do the followings: > ssh people.apache.org > cd /www/hadoop.apache.org/common > svn up The official document will be updated automatically. Now your name is in the PMC list. http://hadoop.apache.org/who.html I'll update the wiki to reflect that. Thanks, Akira On 5/

Re: Hadoop branch-2 build is broken

No, I think it is this commit: https://github.com/apache/hadoop/commit/e205421555841dbf482d6aa1464cc15788b2b1fb (HADOOP-13157). On Tue, May 17, 2016 at 6:13 PM, Xiaoyu Yao wrote: > Hadoop Branch-2 build is broken by this commit. > > ac8fb579c6058fec60caf30682f902413d68edf3: "Remove parent's env

[jira] [Created] (HADOOP-13168) Support Future.get with timeout in ipc async calls

Tsz Wo Nicholas Sze created HADOOP-13168: Summary: Support Future.get with timeout in ipc async calls Key: HADOOP-13168 URL: https://issues.apache.org/jira/browse/HADOOP-13168 Project: Hadoop C

Hadoop branch-2 build is broken

Hadoop Branch-2 build is broken by this commit. ac8fb579c6058fec60caf30682f902413d68edf3: "Remove parent's env vars from child processes” [ERROR] COMPILATION ERROR : [INFO] - [ERROR] /Users/xyao/hadoop/hadoop-common-project/hadoop-comm

Re: Release numbering for 3.x leading up to GA

The sooner the better for incompatible changes, but at this point we are explicitly not guaranteeing any compatibility between alpha releases. For EC, my understanding is that we're still working on the coder configuration. Given that we're still working on L&N changes, I think it's possible that

Jenkins build is back to normal : Hadoop-common-trunk-Java8 #1498

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

Re: Different JIRA permissions for HADOOP and HDFS

We should probably just remove a big chunk of the committers from all the lists. Most of them have disappeared from Hadoop anyway. (The 55% growth in JIRA issues in patch available state in the past year alone a pretty good testament to that fact.) > On May 17, 2016, at 4:40 PM, Akira Ajisak

Re: Release numbering for 3.x leading up to GA

Naming convention looks good. Thanks Andrew for driving this! Could you explain a little more on the criteria of cutting alpha1 / alpha2? What are the goals we want to achieve for alpha1? From EC's perspective, maybe we should target on having all compatibility-related changes in alpha1, like new

Re: Different JIRA permissions for HADOOP and HDFS

> Is there some way for us to add a "Contributors2" group with the same > permissions as a workaround? Or we could try to clean out contributors > who are no longer active, but that might be hard to figure out. Contributors2 seems fine. AFAIK, committers sometimes cleaned out contributors who a

Build failed in Jenkins: Hadoop-common-trunk-Java8 #1497

See Changes: [xyao] HADOOP-13159. Fix potential NPE in Metrics2 source for [jing9] HDFS-10397. Distcp should ignore -delete option if -diff option is -- [...truncated 5135 lines...] Te

Build failed in Jenkins: Hadoop-common-trunk-Java8 #1496

See Changes: [yzhang] HDFS-9732, Improve DelegationTokenIdentifier.toString() for better [junping_du] MAPREDUCE-6657. Job history server can fail on startup when NameNode is [jianhe] Addendum patch for YARN-4832. Contribute

Re: [DISCUSS] upgrade tomcat from 6.0.44 to 6.0.45 and use non apache.org mirror

> On May 17, 2016, at 2:08 PM, Wangda Tan wrote: > > Then I investigated a little more, there're two issues from what I can see > 1) If you look at http://archive.apache.org/dist/, it clearly says: > *> Please do not download from apache.org !* > > 2) And also, http://archive

Jenkins build is back to normal : Hadoop-common-trunk-Java8 #1495

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

[DISCUSS] upgrade tomcat from 6.0.44 to 6.0.45 and use non apache.org mirror

Hi common-devs, When I tried to build Hadoop trunk today, Maven build failed because kms failed to download: http://archive.apache.org/dist/tomcat/tomcat-6/v6.0.44/bin/apache-tomcat-6.0.44.tar.gz . When I open the link from browser, it shows bandwidth limit exceeded: === Bandwidth limit exceeded

Help with committing document to home.apache.org

Hi, Would someone help to clarify the current approach to publish the Hadoop's official document? Since people.apache.org being moved to home.apache.org, the server does not allow ssh logins. Thus the instructions on wiki (https://wiki.apache.org/hadoop/HowToCommit) is not valid anymore: svn co

Re: [DISCUSS] Release blocker HADOOP-12893 (LICENSE and NOTICE files)

Re: src-only release The primary way people consume our artifacts is the binary tarball and more importantly the Maven artifacts. Our downstreams aren't going to integrate and test without Maven artifacts. Thus (unfortunately) I don't see a src-only release being very useful. We used to say "the

Build failed in Jenkins: Hadoop-common-trunk-Java8 #1494

See Changes: [cmccabe] HDFS-10404. Fix formatting of CacheAdmin command usage help text (Yiqun [jianhe] YARN-4832. NM side resource value should get updated if change applied -- [...t

Re: Different JIRA permissions for HADOOP and HDFS

Hat tip to Steve for this tip, what's broken is autocomplete. If you type in the username and click "Save", it'll still go through. FWIW, I've also had success with autocomplete using a Firefox private browser. On Tue, May 17, 2016 at 11:16 AM, Robert Kanter wrote: > We've also had a related lo

Re: Different JIRA permissions for HADOOP and HDFS

We've also had a related long-standing issue (or at least I have) where I can't add any more contributors to HADOOP or HDFS because JIRA times out on looking up their username. I'm guessing we have too many contributors for those projects. I bet YARN and MAPREDUCE are close. Is there some way fo

Re: Tons of "javac: invalid target release: 1.8" failures happen on YARN precommit runs

Thanks Allen, I just triggered other tests to run, will report here if any other issues found. - Wangda On Tue, May 17, 2016 at 11:10 AM, Allen Wittenauer wrote: > > > On May 17, 2016, at 10:54 AM, Wangda Tan wrote: > > > > Hi YARN-dev/Common-dev, > > > > I noticed lots of "javac: invalid tar

Re: Different JIRA permissions for HADOOP and HDFS

Similar issue for me. I can't modify HDFS and HADOOP JIRAs now. -Ray On Tue, May 17, 2016 at 9:54 AM, Varun Saxena wrote: > Hi, > > I do not have permissions for any project other than YARN as well. Unable > to assign a JIRA in MAPREDUCE for instance. > Can somebody give me permission ? > > R

Re: Tons of "javac: invalid target release: 1.8" failures happen on YARN precommit runs

> On May 17, 2016, at 10:54 AM, Wangda Tan wrote: > > Hi YARN-dev/Common-dev, > > I noticed lots of "javac: invalid target release: 1.8" failures happen on > YARN precommit runs since yesterday, not sure if other projects like HDFS > face the same issue. > > Filed HADOOP-13167 to track the iss

[jira] [Resolved] (HADOOP-13167) "javac: invalid target release: 1.8" failures happen on YARN precommit jobs

[ https://issues.apache.org/jira/browse/HADOOP-13167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer resolved HADOOP-13167. --- Resolution: Duplicate YARN-5100 ran without incident. Closing as a dupe. > "javac:

Tons of "javac: invalid target release: 1.8" failures happen on YARN precommit runs

Hi YARN-dev/Common-dev, I noticed lots of "javac: invalid target release: 1.8" failures happen on YARN precommit runs since yesterday, not sure if other projects like HDFS face the same issue. Filed HADOOP-13167 to track the issue. Thanks, Wangda

[jira] [Created] (HADOOP-13167) "javac: invalid target release: 1.8" failures happen on YARN precommit jobs

Wangda Tan created HADOOP-13167: --- Summary: "javac: invalid target release: 1.8" failures happen on YARN precommit jobs Key: HADOOP-13167 URL: https://issues.apache.org/jira/browse/HADOOP-13167 Project:

Re: Different JIRA permissions for HADOOP and HDFS

Hi, I do not have permissions for any project other than YARN as well. Unable to assign a JIRA in MAPREDUCE for instance. Can somebody give me permission ? Regards, Varun Saxena. On Tue, May 17, 2016 at 11:03 AM, Vinayakumar B < vinayakumarb.apa...@gmail.com> wrote: > Thanks Akira. > On 17 May

Build failed in Jenkins: Hadoop-common-trunk-Java8 #1493

See Changes: [jlowe] MAPREDUCE-6701. application master log can not be available when [jlowe] MAPREDUCE-6698. Increase timeout on -- [...truncated 5637 lines...] Running org.apache.had

Jenkins build is back to normal : Hadoop-common-trunk-Java8 #1492

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

Build failed in Jenkins: Hadoop-common-trunk-Java8 #1491

See Changes: [kihwal] HDFS-10303. DataStreamer#ResponseProcessor calculates packet ack latency -- [...truncated 5156 lines...] Running org.apache.hadoop.net.TestTableMapping Running or

[jira] [Created] (HADOOP-13166) add getFileStatus("/") test to AbstractContractGetFileStatusTest

Steve Loughran created HADOOP-13166: --- Summary: add getFileStatus("/") test to AbstractContractGetFileStatusTest Key: HADOOP-13166 URL: https://issues.apache.org/jira/browse/HADOOP-13166 Project: Had

Re: [DISCUSS] Set minimum version of Hadoop 3 to JDK8 (HADOOP-11858)

Thanks to Karthik’s +1, HADOOP-13161 was committed last night and appears to be working. I’ve got almost the entire list of stuff finished. I’m now going to go through the java8 jobs and actually sync them up, since they all do slightly different things. :/ > On May 16, 2016, at 8:0

Re: [DISCUSS] Set minimum version of Hadoop 3 to JDK8 (HADOOP-11858)

> On 16 May 2016, at 23:58, Andrew Wang wrote: > > Very happy to announce that we've committed HADOOP-11858. I'm looking > forward to writing my first lambda in Java. I also attached a video to the > JIRA so we can all relive this moment in Hadoop development history. > > It sounds like there's

Re: [DISCUSS] Release blocker HADOOP-12893 (LICENSE and NOTICE files)

> On 16 May 2016, at 02:43, Andrew Wang wrote: > > Hi common-dev, > > We have a first cut of the L&N files on HADOOP-12893. Many thanks to Xiao > Chen and Akira Ajisaka for doing the brunt of this work. However, full ASF > compliance will require a lot more Maven work. In the meanwhile, our > r

[jira] [Resolved] (HADOOP-13165) S3AFileSystem toString can throw NPE when cannedACL is not set

[ https://issues.apache.org/jira/browse/HADOOP-13165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran resolved HADOOP-13165. - Resolution: Duplicate HADOOP-13130 patch 005 already found and fixed that > S3AFileSyst

Re: [DISCUSS] Release blocker HADOOP-12893 (LICENSE and NOTICE files)

Hi Andrew, Thank you for starting discussion. > We're thinking about a "fix-and-iterate" approach, just to get the currently > ongoing releases out the door. It's a good choice and I agree with you basically. My impression, however, is that we should stop *binary distribution* and we should onl

[jira] [Created] (HADOOP-13165) S3AFileSystem toString can throw NPE when cannedACL is not set

Rajesh Balamohan created HADOOP-13165: - Summary: S3AFileSystem toString can throw NPE when cannedACL is not set Key: HADOOP-13165 URL: https://issues.apache.org/jira/browse/HADOOP-13165 Project: H

Jenkins build is back to normal : Hadoop-common-trunk-Java8 #1487

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

Build failed in Jenkins: Hadoop-common-trunk-Java8 #1486

See Changes: [Arun Suresh] YARN-5075. Fix findbugs warnings in hadoop-yarn-common module. (asuresh) -- [...truncated 5155 lines...] Running org.apache.hadoop.net.TestClusterTopology Te